chore: bump version to 1.2.32

[wjyrich]

update changelog to 1.2.32

Summary by Sourcery

Chores:

• Bump Debian changelog version to 1.2.32

[sourcery-ai]

Reviewer's Guide

This PR performs a straightforward version bump by updating the Debian changelog to reflect release 1.2.32.

File-Level Changes

Change	Details	Files
Updated Debian changelog entry for new version	Incremented version number to 1.2.32 Updated release date metadata Added corresponding changelog notes	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 @wjyrich - 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.}

[github-actions]

TAG Bot

TAG: 1.2.32
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

deepin pr auto review

这个提交的changelog记录了两个修复，分别是添加了硬编码标志到Debian构建规则，以及修复了ApplicationManager1Service::Identify方法中的时间问题。下面是对这个提交的详细审查：

代码审查

1. Changelog格式：

   • Changelog格式正确，每个修复都有对应的描述。
   • 修复描述清晰，有助于其他开发者理解修复的内容。

2. 硬编码标志：

   • 添加硬编码标志到Debian构建规则是一个好的实践，可以提高软件的安全性。
   • 确保这些标志是经过充分测试的，并且不会影响构建过程。

3. 时间问题修复：

   • 修复了ApplicationManager1Service::Identify方法中的时间问题，这是一个重要的修复。
   • 需要确认修复后的代码逻辑是否正确，并且没有引入新的问题。

代码质量

1. 代码注释：

   • 考虑在修复代码中添加注释，说明为什么需要这些硬编码标志，以及修复时间问题的具体逻辑。

2. 代码风格：

   • 确保修复后的代码遵循项目的代码风格指南，保持代码的一致性和可读性。

代码性能

1. 性能影响：

   • 添加硬编码标志可能会对构建时间产生影响，需要评估其对构建性能的影响。

2. 时间问题修复：

   • 确保修复后的代码不会引入性能瓶颈，特别是如果修复涉及到复杂的逻辑或频繁调用的方法。

代码安全

1. 硬编码标志的安全性：

   • 确保添加的硬编码标志不会引入安全漏洞，比如硬编码的密码或敏感信息。

2. 时间问题修复：

   • 确保修复后的代码不会引入安全漏洞，比如未正确处理并发访问或资源竞争。

总结

这个提交的changelog记录了两个重要的修复，并且格式清晰。需要确保修复后的代码经过充分的测试，并且遵循项目的代码风格指南。同时，需要评估硬编码标志对构建性能的影响，并确保修复不会引入新的安全漏洞。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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