chore: bump version to 6.0.52

[mhduiy]

update changelog to 6.0.52

Summary by Sourcery

Chores:

• Bump Debian changelog entry to version 6.0.52.

[github-actions]

TAG Bot

TAG: 6.0.52
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian changelog to reflect the new release version 6.0.52.

File-Level Changes

Change	Details	Files
Update Debian changelog entry for version 6.0.52.	Adjust the top changelog stanza to use version 6.0.52. Refresh associated metadata in the changelog entry as needed for the new 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.

[deepin-ci-robot]

deepin pr auto review

我来对这个debian/changelog的diff进行审查：

1. 语法逻辑：

• changelog格式符合Debian标准，包含了版本号、发行状态(urgent)、维护者信息和时间戳
• 格式正确，使用了标准的changelog条目格式

2. 代码质量：

• 版本号从6.0.51升级到6.0.52，符合语义化版本规范
• 维护者信息格式正确，包含姓名、邮箱和提交时间
• 时间戳格式符合标准(使用RFC 2822格式)

3. 代码性能：

• 作为changelog文件，性能不是主要考虑因素
• 文件大小合理，没有冗余内容

4. 代码安全：

• 没有暴露敏感信息
• 邮箱地址是公开的维护者邮箱，没有安全风险

改进建议：

1. 建议在changelog条目中添加更详细的变更说明，而不仅仅是"Release 6.0.52"。可以具体说明这个版本包含的主要改动或修复的问题。

2. 时间显示为2025年12月25日，这可能是一个将来的日期。建议确认这是否是正确的发布日期，如果是测试用的，建议修改为当前日期。

3. 建议在变更说明中使用更具体的动词，比如：

   • "Fixed: 修复了XXX问题"
   • "Added: 新增了XXX功能"
   • "Updated: 更新了XXX依赖"

4. 考虑添加一个变更类型的标记，比如：

   • [Security] 安全相关更新
   • [Feature] 新功能
   • [Bugfix] 错误修复
   • [Translation] 翻译更新

这些改进会让changelog更加规范和有用，便于其他开发者或用户了解版本的具体变更内容。

[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: BLumia, 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