chore: [tag] New tag v1.0.12

[re2zero]

v1.0.12 release.

Log: New tag v1.0.12.

Summary by Sourcery

Chores:

• Update Debian changelog to prepare for v1.0.12 release

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the debian changelog file to reflect the new tag v1.0.12.

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

File-Level Changes

Change	Details	Files
Updated the debian changelog file to reflect the new tag v1.0.12.	Updated the version number in the changelog. Added a new entry for the v1.0.12 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.

[deepin-ci-robot]

deepin pr auto review

这个提交的改动主要是更新了changelog文件，添加了一个新的版本记录。从代码审查的角度来看，这个改动是合理的，但以下几点需要注意：

1. 版本号一致性：确保版本号1.0.12与代码库中的实际版本号一致，避免出现版本号不一致的情况。

2. 描述清晰性：在changelog中添加的描述应该清晰明了，以便其他开发者或用户能够快速理解这次更新的内容。例如，feat: Remove displayjack kvm depend.可以更具体地描述移除依赖的原因或影响。

3. 格式一致性：检查changelog文件的格式是否与项目中的其他记录保持一致，包括日期格式、作者信息等。

4. 版本更新记录：确保在changelog中记录了所有重要的版本更新，包括新增功能、修复的bug、性能改进等。

5. 依赖管理：移除displayjack kvm依赖后，需要确认是否有其他依赖项需要更新，以确保系统的稳定性和兼容性。

6. 测试：在更新changelog后，建议进行相关的测试，确保移除依赖后，功能仍然正常工作，没有引入新的问题。

7. 文档更新：如果移除依赖项会影响用户的使用，需要更新相关的文档，告知用户如何处理依赖问题。

综上所述，这个提交的改动是合理的，但需要注意以上几点，以确保代码库的稳定性和可维护性。

[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.}

[github-actions]

TAG Bot

TAG: 1.0.12
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lzwind, 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