chore: update changelog to 1.0.22

[mhduiy]

更新说明

自动更新 changelog 到版本 1.0.22

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

• Refresh debian/changelog entries to reflect version 1.0.22.

[github-actions]

TAG Bot

TAG: 1.0.22
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Debian packaging changelog metadata to bump the package version to 1.0.22 on master.

File-Level Changes

Change	Details	Files
Bump Debian package changelog entry to version 1.0.22.	Add or update the latest changelog stanza to reflect version 1.0.22. Ensure the changelog format remains valid for Debian tooling (dch, dpkg-buildpackage, etc.). Align the recorded target branch/release information with the master branch for this version.	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 软件包的变更日志文件，用于记录软件包的版本更新历史。以下是对该 git diff 的详细审查和改进建议：

1. 语法与格式审查

• 格式规范：该变更日志严格遵循了 Debian 的 changelog 格式规范（package (version) distribution; urgency=comment），包括维护者信息、日期和变更条目。格式正确。
• 语法正确性：文本内容没有语法错误。

2. 逻辑审查

• 版本号递增：版本号从 1.0.21 增加到了 1.0.22，符合版本控制的逻辑。
• 内容一致性：变更内容 "implement wallpaper cache plugin"（实现壁纸缓存插件）与版本号变更相匹配，表明这是一个新功能的添加。

3. 代码质量与文档

• 描述清晰度：变更描述 feat: implement wallpaper cache plugin for dde-services 比较清晰，使用了常见的 feat: 前缀来表明这是一个新功能。这有助于阅读者快速识别变更类型。
• 详细程度：对于 changelog 来说，目前的描述是可以接受的。但如果这是一个复杂的插件，建议在提交信息或相关的代码文档中提供更详细的实现细节或设计文档链接。

4. 代码安全

• 潜在风险：引入"壁纸缓存"功能通常涉及文件读写操作。虽然这里只是日志条目，但在实际代码审查中应关注：
  • 缓存文件的存储位置是否安全（权限控制）。
  • 缓存的大小是否有上限，防止磁盘空间被耗尽（DoS 风险）。
  • 缓存数据的清理机制是否完善。
  • 如果涉及网络传输（例如缓存网络壁纸），是否验证了数据来源的安全性。

5. 性能影响

• 正面影响：壁纸缓存插件的主要目的通常是为了提升性能（减少加载时间）。从描述上看，这是一个性能优化的举措。
• 潜在开销：需要关注缓存管理本身带来的内存和 CPU 开销是否在可接受范围内。

6. 改进建议

尽管 changelog 本身写得不错，但为了提高项目的可维护性和专业性，可以考虑以下建议：

1. 日期异常检查：

   • 问题：日期显示为 Fri, 24 Apr 2026。当前时间显然早于 2026 年。
   • 建议：请检查系统时间或提交时间设置。使用未来的日期可能会导致打包系统（如 dpkg-buildpackage）发出警告，或者在时间同步后导致版本混乱。请将其修改为当前正确的日期。

2. 变更描述细化（可选）：

   • 如果该插件引入了新的依赖库，建议在 changelog 中补充说明（例如：* Added dependency: libxyz）。
   • 如果该变更涉及配置文件的变更，建议提示用户注意。

3. 发布分支：

   • unstable 发行版通常是用于开发中的版本。如果这是一个准备发布的稳定版更新，请确认 distribution 字段是否应改为 stable 或具体的发行版代号（如 bullseye）。

总结：除了日期明显错误（使用了未来的时间）外，该 changelog 条目格式规范、描述清晰。建议修正日期后再进行提交。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

[wjyrich]

/forcemerge

[deepin-bot]

This pr force merged! (status: blocked)

[deepin-bot]

TAG Bot

✅ Tag created successfully

📋 Tag Details

• Tag Name: 1.0.22
• Tag SHA: 246402362b397f6a82eaa4a2e804ad59499c744e
• Commit SHA: f2d2f911285aa223938e1159790955ec615e7da0
• Tag Message:

  Release dde-services 1.0.22
  
  

• Tagger:
  • Name: mhduiy
• Distribution: unstable