feat: update changelog and version

[pengfeixx]

Update changelog and version

Summary by Sourcery

Chores:

• Prepare project for a new version release by updating the Debian changelog

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the changelog and version files to reflect the latest 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.	Added a new entry to 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!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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

这个提交的改动主要是更新了deepin-compressor的版本号，从6.5.3升级到6.5.4。从代码审查的角度来看，这个提交没有明显的语法或逻辑错误。然而，有几个方面可以进一步改进：

1. 版本号更新说明：在提交信息中，只提到了“New version 6.5.4”，但没有说明具体更新了哪些内容。建议在提交信息中详细说明版本更新的内容，以便其他开发者或维护者能够快速了解这次更新的目的和影响。

2. 提交格式：虽然提交信息格式基本正确，但建议使用更规范的提交信息格式，例如遵循Angular提交规范。这样可以提高提交信息的可读性和可维护性。

3. 版本号管理：确保版本号的更新遵循项目的版本管理策略，例如遵循语义化版本控制（Semantic Versioning）。如果项目使用的是语义化版本控制，那么版本号的更新应该遵循以下规则：

   • 主版本号（Major Version）：当你做了不兼容的 API 修改，
   • 次版本号（Minor Version）：当你添加了向下兼容的功能，
   • 修订号（Patch Version）：当你做了向下兼容的问题修正。

4. 测试：在更新版本号后，建议进行相应的测试，以确保新版本的功能和稳定性。

综上所述，虽然这个提交本身没有问题，但可以通过改进提交信息、遵循规范的提交格式、确保版本号管理以及进行测试来提高代码质量和维护性。

[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.}

[github-actions]

TAG Bot

TAG: 6.5.4
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