Skip to content

chore: update version to 6.0.31#144

Merged
lzwind merged 1 commit intolinuxdeepin:masterfrom
wyu71:master
Apr 17, 2026
Merged

chore: update version to 6.0.31#144
lzwind merged 1 commit intolinuxdeepin:masterfrom
wyu71:master

Conversation

@wyu71
Copy link
Copy Markdown
Contributor

@wyu71 wyu71 commented Apr 17, 2026

  • bump version to 6.0.31

Log : bump version to 6.0.31

Summary by Sourcery

Chores:

  • Update Debian packaging metadata to reflect version 6.0.31.

- bump version to 6.0.31

Log : bump version to 6.0.31
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Apr 17, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates package metadata to version 6.0.31 in the Debian packaging changelog.

File-Level Changes

Change Details Files
Update project/package version to 6.0.31 in Debian packaging metadata.
  • Increment the recorded version number to 6.0.31 in the Debian changelog entry.
  • Adjust the associated changelog log message to reflect the new 6.0.31 version.
debian/changelog

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@github-actions
Copy link
Copy Markdown

TAG Bot

TAG: 6.0.31
EXISTED: no
DISTRIBUTION: unstable

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@deepin-ci-robot
Copy link
Copy Markdown

deepin pr auto review

这段代码是一个 Debian 软件包的变更日志(debian/changelog)的 diff 输出。针对这段内容,我将从格式规范和语义逻辑两个方面进行审查,并提出改进意见。

1. 审查结果

整体评价:
该 diff 内容符合 Debian changelog 文件的标准格式要求(遵循 debchangedch 工具的规范),格式正确,语法无误。语义上清晰地表达了版本更新、修复内容及作者信息。

2. 详细审查意见

A. 格式规范

  • 符合标准:格式严格遵循 package (version) distribution; urgency=priority 的头部格式,以及 * key: description 的变更条目格式和 -- author date 的尾部格式。缩进使用正确(条目前为两个空格,作者前为两个空格加两个连字符)。
  • 日期格式:日期格式 Thu, 17 Apr 2026 10:30:00 +0800 符合 RFC 5322 标准。

B. 语义逻辑

  • 版本号:版本号从 6.0.30 升级到 6.0.31,符合版本递增逻辑。
  • 变更描述
    • fix: use dynamic integer range from fcitx5 config properties
    • 描述清晰,指明了这是一个修复(fix),并解释了修复的具体内容(使用 fcitx5 配置属性中的动态整数范围)。
  • 时间戳异常(重要)
    • 日期显示为 2026 年。除非这是一个时间旅行者提交的代码,或者系统时间严重错误,否则这是一个明显的错误。通常 changelog 应该记录提交时的实际时间。

3. 改进建议

1. 修正日期(必须修改)

问题:年份 2026 极有可能是笔误或系统时间错误。
建议:请将年份修正为当前实际年份(例如 20242025,视当前实际时间而定)。
修改示例

- -- Wang Yu <wangyu@uniontech.com>  Thu, 17 Apr 2026 10:30:00 +0800
+ -- Wang Yu <wangyu@uniontech.com>  Thu, 17 Apr 2024 10:30:00 +0800

2. 优化变更描述(可选)

问题:当前的描述 fix: use dynamic integer range... 比较技术化,对于非核心开发者可能不够直观。
建议:如果这个修复解决了用户可见的 Bug(例如:之前设置数值时范围不对导致崩溃或无法保存),可以在描述中简要提及用户层面的影响。
修改示例

-   * fix: use dynamic integer range from fcitx5 config properties
+   * fix: use dynamic integer range from fcitx5 config properties to fix invalid value issues.

3. 代码质量与安全(关联性)

虽然这是 changelog 文本,不涉及直接执行代码,但既然提到了 fix,建议确保对应的代码提交确实解决了以下潜在问题:

  • 逻辑安全性:确保从 fcitx5 获取的"动态整数范围"经过了边界检查,防止因配置文件异常导致的数组越界或整数溢出。
  • 性能:确保获取动态范围的操作不会在 UI 渲染的主线程中进行耗时过长的阻塞操作(例如涉及复杂的 IPC 通信)。

总结

该 diff 文本格式规范,唯一需要立即修正的是日期年份错误。建议在合并前修正时间戳,以保持版本历史的准确性。

@deepin-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lzwind, wyu71

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@lzwind lzwind merged commit 4f54c90 into linuxdeepin:master Apr 17, 2026
13 of 15 checks passed
@deepin-bot
Copy link
Copy Markdown

deepin-bot Bot commented Apr 17, 2026

TAG Bot

Tag created successfully

📋 Tag Details
  • Tag Name: 6.0.31
  • Tag SHA: 7dff5c8f59fb311fd8a05d0906355cc0af03901e
  • Commit SHA: 6b0d118d6b3e24f8d030490fb37499feedba38ba
  • Tag Message:
    Release deepin-fcitx5configtool-plugin 6.0.31
    
    
  • Tagger:
    • Name: wyu71
  • Distribution: unstable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants