chore: update changelog to 20260528144800

[mhduiy]

更新说明

自动更新 changelog 到版本 20260528144800

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

• Refresh package changelog entries to reflect version 20260528144800.

[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

[github-actions]

TAG Bot

TAG: 20260528144800
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian changelog to a new version entry 20260528144800 on master, adjusting only the changelog metadata/content.

File-Level Changes

Change	Details	Files
Update Debian changelog to new version 20260528144800.	Add or modify a changelog entry reflecting version 20260528144800. Ensure metadata (version, date, possibly maintainer and description) matches the new release. Align changelog entry with project’s release process targeting master branch.	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.

[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 文件的修改，添加了一条新的版本更新日志，记录了针对“空图像导致采集卡死”问题的修复。

以下是我的详细审查意见：

1. 语法逻辑

• 格式规范：Debian Changelog 有着非常严格的格式要求。你提供的变更在格式上是正确的：
  • 版本号、发行版（unstable）和紧急程度（urgency=medium）之间用空格分隔。
  • 修改说明以两个空格开头，并符合常规的提交信息规范（fix: ...）。
  • 维护者信息格式正确（ -- 姓名 <邮箱> 日期），注意日期前面的两个空格符合规范。
  • 日期格式遵循 RFC 2822 标准（Thu, 28 May 2026 14:48:02 +0800），星期、日、月、年、时间和时区均正确且对应。
• 逻辑：新增条目放在了文件的最上方，符合 Changelog 按时间倒序排列的逻辑。

2. 代码质量

• 语义清晰：提交信息 fix: prevent capture stuck on null images 简明扼要，清楚地说明了修复的问题（采集卡死）以及原因（空图像），符合良好的提交规范。
• 改进建议：虽然当前描述已经不错，但在 Debian Changelog 中，如果修复了特定的 Bug，通常会附上 Bug 编号以便追踪。如果你们项目内部有对应的缺陷追踪系统（如 Jira, GitLab Issues 等），建议在描述中加上相关链接或 ID，例如：fix: prevent capture stuck on null images (Closes: #12345)。

3. 代码性能

• 影响评估：debian/changelog 是纯文本的构建元数据文件，不参与核心代码的运行时逻辑，因此对程序性能没有任何影响。

4. 代码安全

• 影响评估：该变更本身不存在安全风险。
• 潜在关联风险：从描述 prevent capture stuck on null images 可以推测，代码层面可能修复了一个空指针解引用或未处理空图像数据的缺陷。虽然 Changelog 本身安全，但请确保对应的代码修复中，对“空图像”的处理是稳健的（例如：是丢弃该帧并继续采集，还是安全地报错退出？），避免因为处理空图像而引入新的内存泄漏或越界访问风险。

💡 附加提醒

• 时间旅行：提交记录中的日期是 2026-05-28，这是一个未来的时间。请确认这是否是你本地系统时间设置错误导致的。在构建 Debian 包时，如果 Changelog 的时间与实际构建时间差异过大，有时可能会引起构建系统或快照还原工具的警告。
• 代码审查完整性：本次 Diff 仅包含了 Changelog 的更新。通常，修复 Bug 需要伴随实际的源代码修改。请确保在合并代码前，也一并审查了处理“空图像”逻辑的 C++/C 代码变更，确保空指针检查等防御性编程措施已正确实施。

总体而言，这是一次非常标准且规范的 Changelog 更新，没有需要修改的硬性错误，继续保持这种清晰的提交记录习惯！

[deepin-bot]

TAG Bot

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