chore: update changelog to 20260528142155

[mhduiy]

更新说明

自动更新 changelog 到版本 20260528142155

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

• Bump Debian changelog metadata to the new release version 20260528142155.

[deepin-ci-robot]

[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:

• debian/deepin/OWNERS

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian changelog metadata to reflect the new release version 20260528142155 targeting master.

File-Level Changes

Change	Details	Files
Refresh Debian changelog entry for new release version 20260528142155.	Update the top changelog stanza to the new version identifier 20260528142155. Adjust associated metadata in the changelog (e.g., date, description) to match the new release entry.	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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

TAG Bot

TAG: 20260528142155
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

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 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[deepin-ci-robot]

deepin pr auto review

你好！我是智能编程助手 CodeGeeX。我已仔细审查了你提供的 Git Diff 内容。

本次提交是一个 Debian changelog 的更新，记录了版本号为 20260528142155 的更新，主要修复了“防止捕获空图像时卡住”的问题。

针对这部分改动，我将从语法逻辑、代码质量、代码性能、代码安全四个维度提出审查意见和改进建议：

1. 语法与逻辑

• 版本号格式不规范：新版本号使用了 20260528142155（看起来像是一个时间戳：2026年5月28日14:21:55），而前一个版本号是 2.0.12。在 Debian 的版本控制规范中，这种突兀的版本号跳跃和格式变化是不符合常规的。
  • 风险：如果上游或下游包管理器进行版本比较时，可能会因为版本号格式不一致导致升级逻辑混乱或失败。
  • 建议：建议遵循语义化版本号规范，或者 Debian 标准的版本号递增规则。如果是为了体现日期，通常采用 <主版本>.<次版本>.<修订号>+<日期> 的形式，例如 2.0.13 或 2.1.0。

2. 代码质量

• Changelog 描述过于简略：描述信息 fix: prevent capture stuck on null images 虽然指出了修复的现象（防止空图像卡住），但缺乏根本原因的说明。
  • 建议：优秀的 Changelog 应该让维护者或用户清楚“为什么”会卡住。建议补充触发条件或根本原因，例如：fix: prevent capture stuck when receiving null images by adding null check before processing。
• 时间戳异常（未来时间）：变更记录的时间是 Thu, 28 May 2026 14:21:58 +0800，这是一个未来的时间（2026年）。
  • 风险：虽然可能是开发者的系统时间设置错误，但在构建系统和 CI/CD 流水线中，未来时间的包可能会被拒绝，或者导致基于时间的排序和缓存机制出现异常。
  • 建议：请确认生成该 changelog 的系统时间是否准确，确保使用当前的真实 UTC 或本地时间。

3. 代码性能

• 无法直接评估：由于本次 Diff 仅涉及 debian/changelog 文件，未包含实际的 C++/C 或其他业务代码，因此无法对“防止空图像卡住”的具体实现进行性能评估。
• 潜在关注点：根据 Changelog 描述，修复了“空图像卡住”的问题。通常这种卡住可能是由于死循环、互斥锁未释放或阻塞等待引起的。如果在实际代码中是通过增加超时机制来修复的，请关注超时等待是否会降低正常情况下的捕获性能；如果是通过增加判空跳过修复的，则对性能通常有正向提升。

4. 代码安全

• 空指针/空引用的隐患：Changelog 提到了 null images。在底层的图像处理代码中，如果仅仅是在捕获阶段“跳过”或“忽略”了空图像，而没有向上层抛出异常或返回错误码，可能会导致上层业务逻辑在不知情的情况下处理损坏或未初始化的内存数据，这可能引发内存泄漏或空指针解引用等安全问题。
  • 建议：请审查对应的业务代码改动，确保对 null images 的处理不仅仅是 break 或 continue，而是有完善的错误处理链路，确保资源被正确释放，且调用方能妥善处理此异常状态。

---

💡 综合改进建议

如果你有权限修改本次提交，建议调整 changelog 如下：

-deepin-face (20260528142155) unstable; urgency=medium
+deepin-face (2.0.13) unstable; urgency=medium

-  * fix: prevent capture stuck on null images
+  * fix: prevent capture stuck on null images by adding null check and proper error handling to avoid deadlocks
 
- -- zhangkun <zhangkun2@uniontech.com>  Thu, 28 May 2026 14:21:58 +0800
+ -- zhangkun <zhangkun2@uniontech.com>  Tue, 24 Oct 2023 10:00:00 +0800  /* 修改为当前真实时间 */

后续请求：如果你希望我对具体的代码逻辑、性能和安全性做更深入的审查，请提供包含实际业务代码（如处理图像捕获的函数）的 Git Diff，我将为你提供更详尽的分析！

[deepin-bot]

TAG Bot

New tag: 2.0.13
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #52