chore: bump version to 2.0.1

[mhduiy]

update changelog to 2.0.1

Summary by Sourcery

Chores:

• Bump version in debian/changelog to 2.0.1

[sourcery-ai]

Reviewer's Guide

This PR updates the Debian package changelog for the 2.0.1 release by bumping the version number, setting the release date, and adding the new release entry.

File-Level Changes

Change	Details	Files
Bumped Debian changelog version to 2.0.1	Updated the version string to 2.0.1 Set the release date for the 2.0.1 entry Added placeholder entry notes for the new 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!

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

这个提交的改动主要是更新了 dde-session 的版本号，并添加了一个修复项的描述。从代码审查的角度来看，这个提交没有实际的代码改动，只是更新了 changelog 文件。以下是对这个提交的一些改进建议：

1. 版本号更新：确保版本号 2.0.1 是基于 2.0.0 的合理更新，并且遵循了语义化版本控制的原则。

2. 描述清晰性：在 changelog 文件中，修复项的描述 "cannot receive ActiveChanged signal when os was restarted" 应该更详细地说明问题是如何被修复的，以及修复的具体实现细节。这有助于其他开发者理解问题的背景和解决方案。

3. 格式一致性：虽然这个提交的格式基本正确，但建议检查整个 changelog 文件，确保所有条目的格式和风格保持一致。

4. 时间戳准确性：时间戳 Mon, 23 Jun 2025 21:28:59 +0800 应该是提交时的准确时间，确保没有错误。

5. 签名完整性：确认 zhangkun <zhangkun2@uniontech.com> 是提交者的真实信息，并且签名是正确的。

6. 版权声明：如果 dde-session 是一个开源项目，确保在 changelog 文件中包含适当的版权声明。

7. 提交信息格式：虽然这个提交的格式基本正确，但建议遵循标准的提交信息格式，例如使用 type(scope): subject 的格式，其中 type 是提交的类型（如 fix, feat, chore 等），scope 是影响的范围（可选），subject 是简短的描述。

综上所述，这个提交主要是文档性质的更新，没有实际的代码改动。建议在未来的提交中，确保每个提交都包含具体的代码改动，并且提交信息清晰、准确。

[github-actions]

TAG Bot

TAG: 2.0.1
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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