Skip to content

chore: update changelog to 2.0.12#46

Merged
robertkill merged 1 commit into
linuxdeepin:masterfrom
mhduiy:dev-changelog-2.0.12
May 14, 2026
Merged

chore: update changelog to 2.0.12#46
robertkill merged 1 commit into
linuxdeepin:masterfrom
mhduiy:dev-changelog-2.0.12

Conversation

@mhduiy
Copy link
Copy Markdown
Contributor

@mhduiy mhduiy commented May 14, 2026

更新说明

自动更新 changelog 到版本 2.0.12

变更内容

  • 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

  • Bump Debian package changelog entry to version 2.0.12.

update changelog to 2.0.12

Log: update changelog to 2.0.12
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 14, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian changelog metadata to reflect the new 2.0.12 release on the master branch.

File-Level Changes

Change Details Files
Bump Debian package changelog to version 2.0.12.
  • Add a new entry at the top of the Debian changelog for version 2.0.12.
  • Update version metadata and associated release notes in the changelog to match the 2.0.12 release.
  • Ensure the target distribution/branch information in the changelog aligns with master.
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: 2.0.12
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

你好!我是CodeGeeX。我已仔细审查了你提供的 Git Diff 输入。

本次修改主要是对 debian/changelog 文件的更新,添加了版本 2.0.12 的更新日志,并在旧版本 2.0.11 中补充了一条修复记录。

以下是我的审查意见和改进建议:

1. 语法与规范

问题:Debian Changelog 格式规范问题
在 Debian 官方的 changelog 规范中,同一个版本条目下的多个变更记录应当是连续的,不建议在已经发布的历史版本中追加新的条目
在你的 diff 中,你在 2.0.11 的条目下追加了一行 * fix: memory leaks in SNI tooltip and Xembed container window。虽然这在 Git 记录中是允许的,但如果你是在为 2.0.11 打补丁,通常应该增加一个 2.0.11-1 或类似的补丁版本号;如果这个修复已经包含在 2.0.11 的发布中,那么在发布前就应该写好。直接修改历史版本的 changelog 容易导致打包工具(如 dpkg-parsechangelog)或 CI/CD 流水线出现版本解析冲突。

改进建议:
如果 2.0.11 已经发布,请勿修改其条目。如果该内存泄漏修复是促使 2.0.12 发布的原因之一,应将其移至 2.0.12 的条目下:

 deepin-face (2.0.12) unstable; urgency=medium
 
+  * fix: memory leaks in SNI tooltip and Xembed container window
   * fix: resolve face enrollment freeze issue
 
  -- zhangkun <zhangkun2@uniontech.com>  Thu, 14 May 2026 20:03:22 +0800

2. 代码逻辑

问题:时间线逻辑异常
从时间戳来看,2.0.11 的发布日期是 2026年3月18日,而 2.0.12 的发布日期是 2026年5月14日。时间先后顺序是正确的,逻辑上没有问题。
注:年份显示为 2026 年,如果是实际项目请确认是否为笔误(如本应是 2024 或 2025),如果是计划中的发布日期则忽略此条。

3. 代码质量

建议:变更描述的颗粒度可以更细
当前的 changelog 描述如下:

  • fix: resolve face enrollment freeze issue (修复:解决人脸录入卡死问题)
  • fix: memory leaks in SNI tooltip and Xembed container window (修复:SNI tooltip 和 Xembed 容器窗口的内存泄漏)

对于面向用户或维护者的 changelog,描述已经比较清晰。但如果项目规模较大,建议在 changelog 中附带关键的 PR 或 Issue 编号,以便于日后溯源。例如:
* fix: resolve face enrollment freeze issue (#123)
这样能显著提升长期维护时的代码可追溯性。

4. 代码性能与安全

由于本次变更仅涉及纯文本的 changelog 修改,不涉及可执行代码或编译逻辑,因此不存在代码性能或安全方面的影响。


总结:
本次修改主要存在 Debian Changelog 规范 上的小瑕疵(修改了历史版本条目)。建议将追加到 2.0.11 的内存泄漏修复记录移至 2.0.12 的条目中,以符合 Debian 包的维护规范。其余部分符合格式要求,无语法及安全问题。

@deepin-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mhduiy, robertkill

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

@robertkill robertkill merged commit d356549 into linuxdeepin:master May 14, 2026
10 of 12 checks passed
@deepin-bot
Copy link
Copy Markdown
Contributor

deepin-bot Bot commented May 14, 2026

TAG Bot

Tag created successfully

📋 Tag Details
  • Tag Name: 2.0.12
  • Tag SHA: 4908a8b282cb1d3a8d10ecb8ced7eaaebc7f8288
  • Commit SHA: a4660f8eeaf11cc8c6986fae82051cba3dbdbfd9
  • Tag Message:
    Release deepin-face 2.0.12
    
    
  • 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