chore: update changelog

[Lighto-Ku]

update version to 6.5.27

Log: update changelog

Summary by Sourcery

Chores:

• Update Debian changelog to version 6.5.27

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Lighto-Ku

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

[sourcery-ai]

Reviewer's Guide

This PR increments the Debian package version to 6.5.27 and refreshes the corresponding changelog entry.

File-Level Changes

Change	Details	Files
Version bump and changelog refresh	Updated the package version to 6.5.27 Refreshed the changelog entry message Adjusted the release date in the changelog	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 @Lighto-Ku - 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.}

[github-actions]

TAG Bot

TAG: 6.5.27
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

deepin pr auto review

代码审查意见：

1. 版本号更新：

   • 在arm64/linglong.yaml、linglong.yaml和loong64/linglong.yaml文件中，版本号从6.5.26.1更新到6.5.27.1。确认是否有相应的代码更改或功能更新来支持这个版本号的提升。

2. 文件摘要更新：

   • 在arm64/linglong.yaml、linglong.yaml和loong64/linglong.yaml文件中，文件摘要（digest）已更新。确保这些摘要值是正确的，并且与新的文件版本相匹配。

3. changelog更新：

   • 在debian/changelog文件中，新增了一个条目来记录版本6.5.27的更新。这个条目中提到的是“update translations”，请确认这是否是正确的更新内容描述。

4. 文件末尾的空行：

   • 在arm64/linglong.yaml、linglong.yaml和loong64/linglong.yaml文件中，文件末尾的空行被保留。这通常是一个好的实践，因为它有助于保持文件的一致性。

5. 文件权限：

   • 在loong64/linglong.yaml文件中，文件权限被设置为100755。确认这是否是必要的，因为通常YAML文件不需要执行权限。

6. 代码风格和格式：

   • 确保所有YAML文件遵循一致的代码风格和格式。例如，缩进和空格的使用应该一致。

7. 依赖性检查：

   • 确认是否有任何依赖项需要更新，以支持新的版本号或文件摘要。

8. 测试：

   • 在发布新版本之前，确保进行充分的测试，包括单元测试和集成测试，以确保新版本的功能和性能与预期一致。

9. 文档更新：

   • 如果有相关的文档需要更新，确保文档也反映了版本和文件摘要的更改。

10. 安全检查：

    • 确保新版本中没有引入任何已知的安全漏洞。如果可能，进行安全审计和代码审查。

总体来说，这个提交看起来是合理的，但需要确保所有更改都有充分的理由，并且已经过适当的测试和验证。

[lzwind]

/topic cd-20250623

[lzwind]

/integr-topic cd-20250623

[deepin-ci-robot]

Add topic: cd-20250623 successed.

[lzwind]

/integr-topic cd-20250623

[deepin-ci-robot]

Integrated with pr deepin-community/Repository-Integration#2943

[deepin-ci-robot]

Integrated with pr deepin-community/Repository-Integration#2943