chore: bump version to 1.0.31

[18202781743]

update changelog to 1.0.31

Summary by Sourcery

Chores:

• Bump Debian package version to 1.0.31 in changelog

[sourcery-ai]

Reviewer's Guide

The PR updates the Debian changelog to reflect the new package version 1.0.31, modifying the version header and release-date entry for the upcoming release.

File-Level Changes

Change	Details	Files
Bump version and refresh changelog for 1.0.31	Increment version header from 1.0.30 to 1.0.31 Update release date to the current date Adjust changelog entry content to reference 1.0.31	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 @18202781743 - 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

在审查 debian/changelog 文件的更改时，我注意到以下几点：

1. 版本号更新：在提交信息中，版本号从 1.0.30 更新到了 1.0.31，这是一个合理的版本号更新，表示有新的功能或改进。

2. 提交信息格式：提交信息遵循了 Debian 的标准格式，包括版本号、 urgency 等字段，这是正确的。

3. 功能描述：

   • feat: add user configuration cleanup functionality：这个描述清晰地说明了新增的功能，即用户配置清理功能。这是一个好的实践，有助于其他开发者理解这次提交的目的。

4. 重构描述：

   • refactor: simplify CMake version requirements：这个描述说明了重构的内容，即简化了 CMake 的版本要求。这也是一个合理的重构，有助于提高项目的可维护性。

5. 日期和时间：提交日期和时间是正确的，格式也符合 Debian 的要求。

6. 签名：提交者签名是正确的，格式符合 Debian 的要求。

总体来说，这次提交的 debian/changelog 文件改动是合理的，没有发现明显的语法或逻辑错误。但是，为了进一步提高代码质量，可以考虑以下几点：

• 详细描述：在提交信息中，可以进一步详细描述用户配置清理功能的具体实现细节，以及简化 CMake 版本要求的具体方法，这样有助于其他开发者更好地理解这次提交的上下文。
• 一致性：确保所有提交信息都遵循相同的格式和风格，以提高代码库的一致性。

以上是针对 debian/changelog 文件的审查意见，如果有其他部分的代码需要审查，请提供具体的代码内容。

[github-actions]

TAG Bot

TAG: 1.0.31
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 18202781743, mhduiy

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