chore: bump version to 1.0.21

[18202781743]

update changelog to 1.0.21

Summary by Sourcery

Chores:

• Update project version in the Debian changelog file

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the changelog file to reflect the new version 1.0.21.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated the changelog file to reflect the new version 1.0.21.	Updated the version number in the changelog. Added a new entry for version 1.0.21.	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!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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 @18202781743 - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

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

这个提交的changelog文件更新了dde-api-proxy的版本号和更新日志。以下是针对这个提交的一些改进建议：

1. 版本号更新：

   • 确认版本号1.0.21是否正确，并且符合语义化版本控制规则。

2. 更新日志格式：

   • 更新日志中的每一项应该遵循一致的格式，例如：

     - chore: remove unnecessary dependencies
     - chore: license check
     - refact: switch to qt6 for debian
     - feat: adapt to qt6
     

   • 确保每个条目都以 - 开头，并且条目类型（chore, fix, feat, etc.）和描述清晰明了。

3. 更新日志的完整性：

   • 确保更新日志中包含了所有重要的更改，包括但不限于：
     • 移除不必要的依赖项
     • 许可证检查
     • 切换到Qt6
     • 适应Qt6的更改

4. 日期格式：

   • 确保日期格式正确，并且与本地时区相符。例如，Thu, 27 Mar 2025 11:43:12 +0800 是一个有效的格式。

5. 签名：

   • 确保签名部分（-- 和作者信息）格式正确，并且作者信息与提交者一致。

6. 版本号和更新日志的关联：

   • 确保版本号和更新日志中的更改描述一致，以避免混淆。

7. 许可证检查：

   • 如果有许可证检查的更改，确保在更新日志中明确说明，并且提供相关的文档或链接。

8. 依赖项管理：

   • 如果移除了不必要的依赖项，确保这些依赖项不再被其他代码使用，以避免潜在的运行时错误。

9. Qt6的兼容性：

   • 确保所有代码都已经适配了Qt6，并且没有引入新的兼容性问题。

10. 安全漏洞修复：

    • 确保安全漏洞修复已经正确实现，并且更新日志中明确指出修复了哪些安全漏洞。

11. 测试：

    • 在发布新版本之前，确保进行充分的测试，包括单元测试、集成测试和回归测试，以确保新更改不会引入新的问题。

12. 文档更新：

    • 如果有文档需要更新，确保在更新日志中提及，并且文档已经更新。

通过以上建议，可以确保changelog文件的更新更加规范和准确，有助于维护项目的版本历史和文档的准确性。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 18202781743, 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