chore: update version to 6.5.52

[wyu71]

• bump version to 6.5.52

Log : bump version to 6.5.52

Summary by Sourcery

Chores:

• Update project metadata to reference version 6.5.52.1 in linglong.yaml.

[github-actions]

TAG Bot

TAG: 6.5.52
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR performs a routine version bump of the deepin-editor package from 6.5.51.1 to 6.5.52.1 in the Linglong packaging metadata, with no functional or code logic changes.

File-Level Changes

Change	Details	Files
Update package version metadata to 6.5.52.1.	Change Linglong package version field from 6.5.51.1 to 6.5.52.1 Prepare for corresponding changelog entry in debian/changelog (no diff content shown)	linglong.yaml 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

你好！我是CodeGeeX。我已仔细审查了你提供的 Git Diff 输入。

本次提交主要包含了两个部分：一是将 deepin-editor 的版本号从 6.5.51 升级到 6.5.52；二是在 Debian Changelog 中添加了版本更新日志，记录了修复“支持打开被检测为 MIME 子类型的 JSON 文件”的问题。

以下是我对本次代码变更的详细审查意见：

1. 语法逻辑

• Debian Changelog 格式：debian/changelog 的修改符合标准格式。版本号、优先级、更新说明、作者和日期的格式均正确无误，时间戳也使用了正确的 RFC 2822 格式。
• Linglong 配置格式：linglong.yaml 中的版本号同步更新，YAML 语法正确，缩进无误。
• 逻辑一致性：debian/changelog 中的版本号为 6.5.52，而 linglong.yaml 中的版本号为 6.5.52.1。这在逻辑上是可以接受的（通常意味着底包是 6.5.52，而 linglong 打包补丁版本为 1），但需要确认这是否符合你们项目的版本号管理规范。

2. 代码质量

• Commit Message 与 Changelog 一致性：Changelog 中明确指出了此次版本升级的核心内容（fix: support opening JSON files detected as MIME subtype），这是一个很好的实践，便于追溯。
• 建议：本次 Diff 仅包含版本号升级和 Changelog，并未包含实际的业务代码修改（即修复 JSON 文件 MIME 识别的代码）。在实际的代码审查中，建议将业务代码修改与版本号发布分为两次独立的提交，或者在同一个 PR/Diff 中包含业务代码，以便审查者能够验证 Changelog 中声称的修复是否真正生效。

3. 代码性能

• 本次修改仅涉及配置文件和文本文件，不涉及可执行代码或算法逻辑，因此无性能影响。

4. 代码安全

• 日期合理性：Changelog 中的日期为 Wed, 20 May 2026（2026年5月20日）。虽然星期几的计算是正确的（2026年5月20日确实是星期三），但这是一个未来的时间。
  • 风险：如果这是刻意为之（如测试构建系统对未来日期的兼容性）则无妨；但如果是笔误（例如本意是 2023 或 2024），则可能导致 Debian 打包工具（如 dpkg-parsechangelog）因时间逻辑异常发出警告，甚至导致包无法正常发布或升级。
  • 建议：请再次确认该日期是否正确。通常，Debian Changelog 的日期应为代码提交或构建时的真实当前时间，可以使用 date -R 命令生成标准时间。
• 其他安全风险：配置文件中未引入敏感信息或硬编码路径，无其他安全隐患。

总结与改进建议

1. 确认日期：请检查 debian/changelog 中的 2026 年是否为笔误，建议修改为实际提交日期。
2. 补充业务代码：如果这是一个完整的 PR/MR，建议补充修复 JSON MIME 类型识别的实际 C++/QML 代码变更，否则该版本升级缺乏代码支撑。
3. 版本号规范：确认 6.5.52 与 6.5.52.1 的差异是否符合团队规范。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lzwind, wyu71

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

[deepin-bot]

TAG Bot

✅ Tag created successfully

📋 Tag Details

• Tag Name: 6.5.52
• Tag SHA: c5da1892fd66b383fac61a559dbb59c3aec1bd7a
• Commit SHA: f4bf13a45623bf8ac476713079bb37c56d47d863
• Tag Message:

  Release deepin-editor 6.5.52
  
  

• Tagger:
  • Name: wyu71
• Distribution: unstable