chore: update changelog

[pengfeixx]

update changeloog

Log: update changelog

Summary by Sourcery

Chores:

• Update the project's Debian changelog with recent changes

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the changelog file to include the most recent changes.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated the changelog file to reflect the latest changes.	Modified the changelog file.	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 @pengfeixx - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

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

这个提交的改动主要是更新了debian/changelog文件，添加了一个新的版本记录。从代码审查的角度来看，这个改动是合理的，但以下几点需要注意：

1. 版本号一致性：确保新版本号6.5.5与实际代码中的版本号一致，避免版本号不一致导致的混淆。

2. 提交信息清晰：提交信息中提到“New version 6.5.5”，但未说明具体改动内容。建议在提交信息中详细说明新版本引入的功能或修复的bug，以便其他开发者了解改动的背景和目的。

3. 时间戳准确性：提交信息中的时间戳Thu, 24 Apr 2025 20:38:48 +0800是准确的，但需要确认这个时间戳是否反映了实际提交的时间。

4. 版权和作者信息：提交信息中的作者信息xiepengfei <xiepengfei@uniontech.com>是正确的，但需要确保这个信息与实际提交者的信息一致。

5. 格式一致性：debian/changelog文件的格式需要保持一致，包括日期格式、 urgency级别等。

6. 版本号递增：确保版本号的递增是按照语义化版本控制（Semantic Versioning）的规则进行的，即主版本号、次版本号和修订号分别表示不兼容的API更改、向后兼容的功能新增和向后兼容的问题修复。

综上所述，这个提交的改动是合理的，但需要注意版本号的一致性、提交信息的详细性和格式的一致性。

[github-actions]

TAG Bot

TAG: 6.5.5
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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