chore: Bump version to 6.5.3

[re2zero]

Bump version to 6.5.3

Log: Bump version to 6.5.3

Summary by Sourcery

Chores:

• Bump the project version number in the Debian changelog

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: re2zero

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 by Sourcery

This pull request bumps the version of the package to 6.5.3. This is achieved by updating the debian changelog file.

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

File-Level Changes

Change	Details	Files
Bumped the package version to 6.5.3.	Updated the version number in the changelog. Added a new entry for the 6.5.3 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!
• 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.

[sourcery-ai]

Hey @re2zero - 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

这个提交的改动主要是更新了deepin-compressor的版本号，并修复了一个与中文字符加密相关的问题。从提交信息来看，改动是合理的，但以下几点可以进一步优化：

1. 版本号更新：在提交信息中提到将版本号从6.5.2更新到6.5.3，但未提供具体的版本更新内容。建议在提交信息中详细说明版本更新的具体内容，以便其他开发者了解版本更新的影响。

2. 加密问题修复：提交信息中提到修复了与中文字符加密相关的问题，但没有提供修复的具体代码或方法。建议在提交信息中添加修复的详细描述，或者提供修复的代码片段，以便其他开发者了解修复的具体实现。

3. 提交格式：提交信息中的日期格式不符合常见的日期格式，建议使用标准的日期格式，如YYYY-MM-DD。

4. 签名：提交信息中的签名部分使用了re2zero <yangwu@uniontech.com>，建议使用全名和电子邮件地址，以便其他开发者能够更好地识别提交者的身份。

5. 提交信息格式：提交信息中的格式可以更加规范，例如使用统一的缩进和换行符，以提高可读性。

综上所述，建议在提交信息中添加更多的细节，以便其他开发者更好地理解版本更新的内容和修复的方法。同时，建议使用标准的日期格式和规范的提交信息格式，以提高代码的可维护性和可读性。

[lzwind]

/rtest

[lzwind]

/retest

[re2zero]

/retest

[github-actions]

TAG Bot

TAG: 6.5.3
EXISTED: no
DISTRIBUTION: unstable