chore: bump version to 6.0.46

[yixinshark]

as title

Log: as title

Summary by Sourcery

Chores:

• Update Debian changelog to reflect version 6.0.46

[github-actions]

TAG Bot

TAG: 6.0.46
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

deepin pr auto review

根据提供的git diff，我注意到这是一个Debian包的changelog文件变更。让我对此变更进行分析和评价：

1. 版本号变更问题：

• 新版本号从6.0.45跳到了6.0.46，但在中间部分又出现了6.0.45的记录
• 这种版本号的跳跃和回退可能会导致版本管理混乱

2. changelog格式问题：

• changelog条目的顺序应该是从新到旧，但当前diff显示的顺序有些混乱
• 移除了一些版本记录，这可能会导致历史追踪不完整

3. 维护者信息：

• 维护者信息(zyz zhaoyingzhen@uniontech.com)保持一致，这是好的实践

4. 具体变更内容：

• 移除了多个"Sync: from linuxdeepin/dde-session-shell"条目
• 移除了版本号更新("Chore: bump version")的记录
• 移除了移除西班牙语翻译文件的记录

改进建议：

1. 版本管理：

• 建议保持版本号的连续性，避免跳跃和回退
• 确保每个版本变更都有明确的记录和理由

2. changelog格式：

• 严格按照从新到旧的顺序排列版本记录
• 保留所有重要的版本变更记录，即使是一些同步操作

3. 变更记录：

• 对于从其他仓库同步的变更，应该注明具体的变更内容而不仅仅是"Sync"
• 对于版本号更新，应该说明更新的原因

4. 其他建议：

• 考虑将多个连续的"Sync"记录合并为一个，并说明同步的具体内容和范围
• 对于移除翻译文件这样的变更，应该保留记录，说明移除的原因和影响

总的来说，这个diff显示了对changelog文件的大幅修改，主要是移除了一些记录。建议保持changelog的完整性和历史可追溯性，同时确保版本号的连续性和合理性。

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the project version to 6.0.46 by modifying the Debian changelog entry, without altering any functional code.

File-Level Changes

Change	Details	Files
Version bump to 6.0.46	Updated the version number in the changelog header Set the new release date Amended the log entry to reflect the bumped version	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 there - 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: xionglinlin, 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