Skip to content

chore: update changelog to 2.0.28#442

Merged
deepin-bot[bot] merged 1 commit intolinuxdeepin:masterfrom
mhduiy:dev-changelog-2.0.28
Mar 12, 2026
Merged

chore: update changelog to 2.0.28#442
deepin-bot[bot] merged 1 commit intolinuxdeepin:masterfrom
mhduiy:dev-changelog-2.0.28

Conversation

@mhduiy
Copy link
Contributor

@mhduiy mhduiy commented Mar 12, 2026

更新说明

自动更新 changelog 到版本 2.0.28

变更内容

  • 更新 debian/changelog

版本信息

  • 新版本: 2.0.28
  • 目标分支: master

Summary by Sourcery

Chores:

  • Refresh debian/changelog entries to reflect version 2.0.28 targeting master.

update changelog to 2.0.28

Log: update changelog to 2.0.28
@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mhduiy

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

@github-actions
Copy link

TAG Bot

TAG: 2.0.28
EXISTED: no
DISTRIBUTION: unstable

@sourcery-ai
Copy link

sourcery-ai bot commented Mar 12, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian packaging changelog to release version 2.0.28 targeting the master branch.

File-Level Changes

Change Details Files
Bump Debian package changelog entry to version 2.0.28.
  • Add or update the top changelog stanza to version 2.0.28 with appropriate metadata (date/maintainer/message).
  • Ensure the distribution and versioning follow existing Debian changelog conventions.
  • Align the recorded target branch/release information with master for this 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

Copy link

@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

deepin pr auto review

这份 debian/changelog 的 diff 内容主要记录了软件包 dde-tray-loader 从 2.0.27 到 2.0.28 版本的变更。以下是对该变更日志的审查意见,主要针对格式规范和内容准确性:

1. 格式规范审查

  • 符合 Debian 标准:整体格式严格遵循了 Debian changelog 的规范(package (version) distribution; urgency 头部,维护者信息,以及缩进的变更条目)。
  • 缩进正确:每条变更前都有两个空格的缩进,符合标准。
  • 多行处理:关于蓝牙和飞行模式的修复条目使用了正确的换行和缩进(空格+空格+空格),这是处理长行的标准做法。

2. 内容逻辑与语义审查

  • 版本号:版本号从 2.0.27 升级至 2.0.28,符合递增逻辑。
  • 紧急程度urgency=medium 设置合理。虽然包含“防止悬空指针”的安全/稳定性修复和蓝牙功能的修复,但通常只有关键安全漏洞或严重破坏性修复才会使用 highcriticalmedium 是合适的。
  • 变更条目分类
    • i18n:国际化更新,清晰明了。
    • feat:功能重构(使用线程池初始化 SNI 托盘),描述准确。
    • fix:常规错误修复。
    • fix(bluetooth):针对特定模块(蓝牙)的修复,使用了作用域标记,非常规范。

3. 潜在问题与改进建议

  • 日期错误(严重)

    • 问题:维护者行显示的时间是 Thu, 12 Mar 2026
    • 建议:年份写成了 2026,这显然是一个笔误(除非这是为了未来发布的预留)。如果是当前提交,请务必修正为当前年份(如 2024 或 2025)。错误的年份会导致打包工具或版本控制系统产生混淆。
  • 语法与措辞微调

    • 原文fix: prevent dangling pointer in XembedProtocol::onRemoveItemByPid
    • 建议:语法正确,描述清晰。无需修改。
    • 原文fix: resolve touch screen scrolling and clicking issues in bluetooth applet
    • 建议:描述清晰。如果需要更严谨,可以改为 fix(bluetooth): resolve touch screen scrolling and clicking issues,加上作用域前缀与下一条保持一致,但这不是强制的。
    • 原文fix(bluetooth): prevent toggling bluetooth power state in airplane mode
    • 建议:描述准确。

4. 总结

这份 Changelog 的撰写质量很高,分类清晰(使用了 feat, fix, i18n 等前缀),并且涵盖了性能(线程池重构)、稳定性(悬空指针)和功能逻辑(蓝牙交互)的改进。

唯一必须修改的地方是日期中的年份错误。修正日期后,即可合并。

@18202781743
Copy link
Contributor

/forcemerge

@deepin-bot
Copy link

deepin-bot bot commented Mar 12, 2026

This pr force merged! (status: blocked)

@deepin-bot deepin-bot bot merged commit 5422b73 into linuxdeepin:master Mar 12, 2026
10 of 12 checks passed
@deepin-bot
Copy link

deepin-bot bot commented Mar 12, 2026

TAG Bot

Tag created successfully

📋 Tag Details
  • Tag Name: 2.0.28
  • Tag SHA: 190245d46e2c0c81dfdd28c5b86ad451c0821be3
  • Commit SHA: c61252ff34fc53b352aed923eec902c923231e49
  • Tag Message:
    Release dde-tray-loader 2.0.28
    
    
  • Tagger:
    • Name: mhduiy
  • 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