chore: bump version to 6.0.37

[18202781743]

update changelog to 6.0.37

Summary by Sourcery

Chores:

• Bump recorded package version in Debian changelog to 6.0.37.

[github-actions]

TAG Bot

TAG: 6.0.37
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Debian packaging metadata by bumping the package version to 6.0.37 in the changelog.

File-Level Changes

Change	Details	Files
Bump Debian package version to 6.0.37 in changelog.	Update the top changelog entry to reflect version 6.0.37. Adjust associated metadata (e.g., date/maintainer line) if present to match the new release 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]

deepin pr auto review

我来对这个diff进行审查分析：

1. 语法逻辑：

• changelog文件的格式符合Debian的规范，使用了正确的版本号、紧急级别和提交者信息
• 每个变更条目都以"* "开头，格式正确
• [skip CI]标记的使用是合理的，因为这些是翻译更新，不需要触发CI

2. 代码质量：

• 存在一些重复的条目，比如nl(荷兰语)的翻译出现了3次
• 翻译更新的顺序没有按照特定规则排列，建议按照字母顺序或地区分组
• 最后两个非翻译相关的变更("feat"和"i18n"更新)应该放在翻译更新之前，这样更符合变更的重要性排序

3. 改进建议：
   a) 移除重复的翻译条目
   b) 重新组织翻译更新的顺序，可以按字母顺序排列
   c) 将功能性变更(feat)和重要的i18n更新放在翻译更新之前
   d) 考虑将大量的翻译更新合并为一个条目，例如："i18n: Update translations for multiple languages"
   e) 添加更详细的变更描述，特别是对于"移入deepin-login-reminder"这个变更

4. 安全性：

• 这个diff主要涉及翻译更新，不涉及安全相关代码
• 版本号和日期信息看起来是合理的

5. 其他建议：

• 考虑使用自动化脚本来管理翻译更新，避免重复条目
• 可以为翻译更新添加更详细的说明，比如具体更新了哪些内容
• 建议在changelog中添加一个指向完整翻译更新日志的链接（如果有的话）

总体来说，这个changelog更新是合理的，但可以通过一些改进来提高其可读性和维护性。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 18202781743, fly602

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