chore: update changelog to 6.0.33

[mhduiy]

更新说明

自动更新 changelog 到版本 6.0.33

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Documentation:

• Document release 6.0.33 in debian/changelog.

[github-actions]

TAG Bot

TAG: 6.0.33
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This pull request updates the Debian changelog to reflect the new release version 6.0.33 targeting the master branch.

File-Level Changes

Change	Details	Files
Update Debian packaging changelog entry for release 6.0.33.	Add or modify the top changelog stanza to set the version to 6.0.33. Ensure the changelog entry targets the master distribution/branch. Adjust metadata such as date, maintainer, and summary lines as needed to describe the 6.0.33 update.	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.

[deepin-ci-robot]

deepin pr auto review

我来对这个变更进行审查：

1. 语法逻辑：

• changelog 格式符合 Debian 标准，包含了正确的版本号、发行版和紧急程度
• 变更条目使用了标准的 Debian changelog 格式，每个变更前都有正确的缩进和星号
• 维护者信息和时间戳格式正确

2. 代码质量：

• 变更描述清晰简洁，每个变更都准确反映了所做的修改
• 使用了标准的前缀标识变更类型（fix, chore）
• 变更描述具有可读性，能够清楚理解每个变更的目的

3. 代码安全：

• 添加了 "noexecstack" 链接器标志，这是一个很好的安全加固措施，可以防止栈执行
• 使用全局互斥锁解决 X11 线程竞态条件，这是正确的线程安全措施

4. 改进建议：

• 时间戳显示为 2026 年，这明显是一个错误，应该修正为正确的年份
• 建议在变更描述中提供更多细节，例如：
  • 对于 X11 线程竞态条件的修复，可以简要说明具体在什么场景下会出现问题
  • 对于移除 gtk-thumbnailer 模块，可以说明移除的原因（如：已弃用、存在更好的替代方案等）
• 建议在变更描述中添加相关的 bug 编号或 issue 链接（如果有的话）

5. 其他建议：

• 可以考虑在变更描述中添加影响范围说明，帮助用户了解这些变更可能带来的影响
• 对于安全相关的变更（noexecstack），建议在描述中强调其重要性

总体来说，这是一个格式规范、内容清晰的变更记录，主要需要修正时间戳错误，并可以适当增加更多细节信息。

[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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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