chore: bump version to 2025.5.14

[mhduiy]

update changelog to 2025.5.14

Summary by Sourcery

Chores:

• Update debian/changelog version to 2025.5.14

[sourcery-ai]

Reviewer's Guide

This PR updates the Debian package changelog by bumping the version to 2025.5.14 and adjusting the release date accordingly.

File-Level Changes

Change	Details	Files
Updated Debian package changelog to new version	Bumped version number to 2025.5.14 Updated release date in the changelog header	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.

[github-actions]

TAG Bot

TAG: 2025.07.18
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

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

这个提交的改动主要是移除了一个过时的脚本 merge_icons_dstore.py。从提交信息来看，这是一个清理工作，没有引入新的功能或修复bug。以下是对这个提交的一些改进建议：

1. 提交信息格式：提交信息应该简洁明了，并且包含足够的上下文信息。虽然这个提交的提交信息已经比较清晰，但是可以进一步优化，例如：

   deepin-icon-theme (2025.07.18) unstable; urgency=medium
   
     * chore: remove obsolete merge_icons_dstore.py script
   
   -- zhangkun <zhangkun2@uniontech.com>  Fri, 18 Jul 2025 11:08:14 +0800
   

   可以添加一个简短的描述，说明为什么这个脚本被移除，以及移除这个脚本对项目的影响。

2. 脚本移除后的替代方案：如果这个脚本被移除是因为不再需要，那么应该确保项目中没有其他代码依赖于这个脚本。如果有其他代码依赖于这个脚本，那么应该提供替代方案或者更新相关代码。

3. 代码审查：虽然这个提交主要是清理工作，但是建议在移除脚本之前进行代码审查，确保没有遗漏其他相关的代码或配置。

4. 版本号更新：提交信息中的版本号 2025.07.18 和 2025.05.13 看起来是日期格式，但是通常版本号应该是递增的，而不是日期。如果这个提交是版本更新的一部分，那么应该确保版本号是递增的。

5. 文档更新：如果这个脚本在文档中有提及，那么应该更新文档，移除对这个脚本的引用。

6. 测试：如果移除这个脚本可能会影响项目的其他部分，那么应该编写测试来验证移除这个脚本后项目仍然能够正常工作。

综上所述，这个提交是一个清理工作，但是可以通过优化提交信息、确保没有遗漏其他代码、更新文档和编写测试来提高代码质量和维护性。

[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