chore: bump version to 6.0.27

[fly602]

update changelog to 6.0.27

Summary by Sourcery

Build:

• Update debian/changelog to version 6.0.27

[github-actions]

TAG Bot

TAG: 6.0.27
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR bumps the project version to 6.0.27 by updating the Debian changelog with the new release entry.

File-Level Changes

Change	Details	Files
Bump project version and update changelog	Updated version number to 6.0.27 in the changelog header Added new release entry with date and brief notes	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

这是一个 Debian changelog（变更日志）文件的差异，它记录了软件包 dde-api 从版本 6.0.26 到 6.0.27 的更新。让我对这次变更进行分析：

1. 变更内容：

   • 新增了一个版本条目 dde-api (6.0.27)
   • 标记为 unstable 发行版，urgency=medium（中等紧急程度）
   • 更新内容简单，仅标注为 "Release 6.0.27"
   • 维护者信息为 fuleyi [email protected]
   • 时间戳为 2025年9月25日 20:51:52 +0800（北京时间）

2. 评估意见：

   • 语法和格式：符合 Debian changelog 的标准格式，语法正确
   • 信息完整性：基本完整，但更新内容描述过于简单，仅说明是发布新版本，没有具体说明更新内容
   • 时间戳：时间戳是未来的日期（2025年），这可能是误操作或测试用数据

3. 改进建议：

   • 应提供更详细的更新内容说明，例如修复了哪些问题、新增了哪些功能等
   • 检查并修正时间戳，应为当前实际日期而非未来日期
   • 考虑添加变更的分类（如 bug 修复、功能增强、安全更新等）
   • 如果是多个小更新的集合，考虑列出主要变更点

4. 安全性考虑：

   • changelog 本身不涉及安全问题，但信息不完整可能导致用户无法准确评估更新内容
   • 建议在更新内容中明确是否包含安全修复

总体而言，这是一个简单的版本更新 changelog，主要改进点在于提供更详细的更新信息和修正时间戳。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

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