chore: update changelog to 1.0.2

[mhduiy]

更新说明

自动更新 changelog 到版本 1.0.2

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

• Refresh debian/changelog to reflect version 1.0.2 targeting master.

[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

Update Debian package changelog metadata to reflect new release version 1.0.2 targeting master.

File-Level Changes

Change	Details	Files
Refresh Debian changelog entry for the 1.0.2 release.	Adjust package version metadata to 1.0.2 in the changelog header/entry. Update associated changelog text to describe the 1.0.2 release. Ensure the latest changelog stanza is positioned correctly at the top for Debian tooling.	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

这段 debian/changelog 的 diff 内容展示了一个版本从 1.0.1 到 1.0.2 的变更记录。经过审查，我发现其中存在一些逻辑错误、格式规范问题以及潜在的安全隐患。

以下是详细的审查意见和改进建议：

1. 语法逻辑与格式规范

• 时间逻辑错误（严重）：

  • 问题：新版本（1.0.2）的日期是 Thu, 05 Feb 2026，而旧版本（1.0.1）的日期是 Fri, 11 Jan 2025。虽然 changelog 通常是按时间倒序排列的，但这里的年份设定为 2026 年，除非这是为了未来的特定发布计划，否则极有可能是输入错误（可能本意是 2024 或 2025）。
  • 建议：请核实并修正日期年份，确保与实际发布时间一致。

• 重复的日志条目：

  • 问题：在 zhangkun 的部分，* refactor: 调整control 连续出现了两次。
  • 建议：删除重复的条目，保持日志整洁。

• 维护者变更与发行版状态：

  • 问题：版本从 UNRELEASED 变更为 unstable，这是正确的发布流程。但维护者从 echengqi 变更为 zhangkun。这通常意味着打包权责的转移。如果只是临时修改，通常不需要更改最下方的维护者签名行，除非这是新的维护者发布的新版本。
  • 建议：确认是否需要变更维护者。如果是多人协作，通常由最后发布的人签名，但要注意 debian/control 中的 Maintainer 字段是否也需要同步更新。

• 版本号回退风险：

  • 问题：日志中有一行 chore: Bump version to 1.0.1。当前头部版本是 1.0.2。如果在 1.0.2 的变更记录里包含将版本降级到 1.0.1 的记录，会导致版本号混乱。
  • 建议：删除 chore: Bump version to 1.0.1 这一行。Changelog 记录的是当前版本（1.0.2）所做的更改，不应该包含"将版本号改为旧版本"的操作。

2. 代码质量

• 日志信息语言不统一：

  • 问题：日志中混用了英文（如 fix(daemon):, chore:）和中文（如 调整control）。
  • 建议：建议统一使用英文或统一使用中文，以提高日志的可读性和专业性。如果是国际化项目，推荐使用英文。

• Commit Message 格式：

  • 问题：使用了 fix(daemon): 这种类似 Conventional Commits 的格式，这很好。但 refactor: 调整control 比较模糊。
  • 建议：具体说明 control 做了什么调整（例如：refactor(control): update build dependencies），以便于后续追踪变更原因。

3. 代码安全

• 签名验证：
  • 观察：Diff 中显示的是明文签名 -- zhangkun <zhangkun2@uniontech.com>。
  • 建议：虽然这不是语法错误，但在构建发布包时，建议使用 GPG 签名对包进行签名，以确保包的完整性和来源可信度。

4. 改进后的示例

假设修正了年份、删除了重复条目、统一了语言并理顺了版本逻辑，建议的修改如下：

--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,11 @@
-dde-dialog (1.0.1) UNRELEASED; urgency=medium
+dde-dialog (1.0.2) unstable; urgency=medium
 
+  [ zhangkun ]
+  * fix(daemon): dialog-agent displays "null" in pop-up content
+  * refactor(control): update dependencies and package description
   * refactor: 调整control.
 
- -- echengqi <echengqi@uniontech.org>  Fri, 11 Jan 2025 13:40:36 +0800
+ -- zhangkun <zhangkun2@uniontech.com>  Thu, 05 Feb 2025 19:51:43 +0800
 
 dde-dialog (1.0.0) unstable; urgency=medium

主要变更点说明：

1. 修正日期为 2025 年（假设当前是 2025 年）。
2. 删除了 Bump version to 1.0.1 的无效记录。
3. 删除了重复的 refactor 行。
4. 将 refactor: 调整control 改为更具体的描述（示例），或者至少保留一个。
5. 保留了 fix(daemon) 这条有价值的 Bug 修复记录。