chore: bump version to 6.0.31

[18202781743]

update changelog to 6.0.31

Summary by Sourcery

Chores:

• Bump version to 6.0.31.

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 18202781743

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]

Hey @18202781743 - 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. 重复记录：在变更日志中，有多个重复的sync: from linuxdeepin/dtkdeclarative记录。如果这些记录是重复的，应该合并为一个，以保持变更日志的简洁性。

2. 日期格式：提交日期格式应该统一，建议使用YYYY-MM-DD格式，例如2025-02-27。

3. 提交信息：提交信息应该简洁明了，只包含必要的变更描述。如果多个变更记录是相同的，可以合并为一个，并添加一个简短的描述，例如sync: from linuxdeepin/dtkdeclarative。

4. 版本号：确保版本号是正确的，并且与实际代码版本一致。

5. 版权和许可证：如果代码有版权或许可证信息，应该确保在变更日志中注明。

6. 格式化：确保变更日志的格式符合Debian的规范，例如每条记录之间有空行，日期和作者信息格式正确。

改进后的变更日志示例：

dtk6declarative (6.0.31) unstable; urgency=medium

  * sync: from linuxdeepin/dtkdeclarative

 -- YeShanShan <[email protected]>  2025-02-27 20:57:44 +0800

以上是针对变更日志的改进建议，如果这个提交是针对代码的更新，请提供具体的代码内容，以便进行更详细的审查。

[github-actions]

TAG Bot

TAG: 6.0.31
EXISTED: no
DISTRIBUTION: unstable