chore: bump version to 2.0.20

[mhduiy]

update changelog to 2.0.20

Summary by Sourcery

Chores:

• Align Debian packaging changelog with release version 2.0.20.

[github-actions]

TAG Bot

TAG: 2.0.20
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps the Debian package changelog to version 2.0.20 with the corresponding metadata update.

File-Level Changes

Change	Details	Files
Update Debian changelog entry to version 2.0.20.	Adjust the top changelog stanza to reflect version 2.0.20. Update associated changelog metadata fields (e.g., version header, date, or maintainer entry) as needed 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.

[deepin-ci-robot]

deepin pr auto review

我来对这份 git diff 进行审查：

1. 语法逻辑审查：

• changelog 文件的格式符合 Debian 的规范，包含了版本号、发行版、紧急程度以及变更列表
• 每个变更条目都以正确的格式（* 类型: 描述）呈现
• 维护者信息和日期格式符合标准

2. 代码质量评估：

• 变更描述清晰且具体，每个条目都明确说明了修改的目的
• 使用了标准的前缀（chore、fix）来区分不同类型的变更
• 版本号遵循了语义化版本控制规范（2.0.20）

3. 改进建议：

• 可以考虑在变更描述中添加更多技术细节，比如：
  • "chore: switch to use nativeEventFilter" 可以说明为什么需要这个改动，比如是为了提高性能或修复特定问题
  • "fix: disable application theme saving" 可以说明这个修改是为了解决什么具体问题
  • "fix: Fixed the tooltip not following the area format" 可以补充具体的影响范围

4. 安全性考虑：

• 从 changelog 来看，这些修改主要是功能性和维护性的更新，没有涉及安全相关的改动
• 建议在后续版本中如果涉及安全相关修改，应该在 changelog 中明确标注

5. 其他建议：

• 建议在提交信息中使用更一致的时态，比如统一使用现在时或过去时
• 可以考虑在变更描述中添加相关的 bug 编号或 issue 链接，方便追踪
• 对于版本 2.0.20，建议添加更详细的版本说明，特别是如果这是一个包含重要修复的版本

总体来说，这是一个格式规范的 changelog 更新，但可以在描述的详细程度和一致性方面进一步改进。

[sourcery-ai]

Hey - 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[mhduiy]

/forcemerge

[deepin-bot]

This pr force merged! (status: blocked)