chore: bump version to 6.0.32

[mhduiy]

update changelog to 6.0.32

Summary by Sourcery

Chores:

• Align Debian packaging metadata with version 6.0.32 in the changelog.

[github-actions]

TAG Bot

TAG: 6.0.32
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps the Debian package changelog for a new 6.0.32 release without other code changes.

File-Level Changes

Change	Details	Files
Update Debian changelog for version 6.0.32 release.	Add a new changelog entry for version 6.0.32 with appropriate metadata (version, distribution, urgency, maintainer, and timestamp). Document the key changes or release note for 6.0.32 in the changelog entry. Ensure the new entry is prepended so 6.0.32 is the latest visible release.	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

我来对这个git diff进行审查：

1. 语法逻辑：

• changelog的格式符合Debian的规范，版本号、发行版本、紧急程度都正确
• 维护者信息和时间戳格式正确
• 变更条目使用了正确的缩进和格式

2. 代码质量：

• 变更描述简洁明了，准确说明了移除了过时的theme和thumbnail模块
• 版本号从6.0.31升级到6.0.32，符合语义化版本控制规范
• 使用了"chore"作为变更类型，这是一个合适的选择，因为这是一个维护性的改动

3. 代码性能：

• 移除过时的模块是一个好的实践，可以：
  • 减少代码维护负担
  • 降低潜在的安全风险
  • 减少不必要的依赖
  • 提高整体系统性能

4. 代码安全：

• 移除过时的模块有助于提高安全性，因为：
  • 减少了潜在的攻击面
  • 避免了使用可能存在安全漏洞的旧代码
  • 降低了维护复杂性，使安全更新更容易实施

改进建议：

1. 建议在变更描述中更详细地说明为什么这些模块被标记为过时，以及是否有替代方案

2. 可以考虑在变更记录中添加相关的bug编号或issue链接，方便追踪

3. 建议确保所有依赖于这些模块的代码都已经正确迁移或更新

4. 考虑添加向后兼容性说明，如果这个改动可能会影响到其他依赖该API的项目

总体来说，这是一个维护性的改动，格式规范，变更合理。建议补充更多上下文信息以便更好地理解这个改动的完整影响。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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