chore: update changelog to 2.0.28

[mhduiy]

更新说明

自动更新 changelog 到版本 2.0.28

变更内容

• 更新 debian/changelog

版本信息

• 新版本: 2.0.28
• 目标分支: master

Summary by Sourcery

Documentation:

• Refresh Debian changelog documentation to reflect version 2.0.28.

[github-actions]

TAG Bot

TAG: 2.0.28
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the Debian packaging changelog to reflect the new release version 2.0.28 targeting master, without any code or behavior changes.

File-Level Changes

Change	Details	Files
Update Debian package changelog for the 2.0.28 release.	Add or modify the top changelog entry to bump the version to 2.0.28 Adjust associated metadata in the changelog entry (e.g., date, maintainer, or notes) 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.

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

deepin pr auto review

这段 debian/changelog 的 diff 记录了 dde-shell 项目从 2.0.27 到 2.0.28 版本的变更。作为一个代码审查助手，虽然 changelog 本身不包含可执行代码，但它是版本发布和变更历史的关键文档。以下是对该变更日志的审查意见，主要关注其描述的逻辑性、潜在的安全影响以及维护规范：

1. 代码安全与逻辑审查

这是本次变更中最需要关注的部分，涉及到了安全策略的回退。

• 严重关注：回退了通知操作的白名单验证

  • 变更内容：

    Revert "fix: add command whitelist validation for notification actions"
    Revert "fix: update safeCommands whitelist for notification service"
    

  • 风险分析：这两行 Revert 意味着开发者撤销了之前添加的针对通知动作的命令白名单验证机制。
  • 安全建议：
    • 请务必确认回退原因：通常引入白名单是为了防止任意命令执行（RCE）漏洞。回退安全补丁通常意味着该补丁导致了功能不可用或兼容性问题。
    • 替代方案：如果必须回退，请确保有其他安全机制（如沙箱、严格的权限控制）来替代白名单的作用，否则这可能导致严重的安全漏洞。
    • 代码审查关联：在审查对应的代码 diff 时，应重点检查 dde-am 的调用逻辑，确认其本身是否足够安全，或者是否有新的校验逻辑被引入。

• 潜在风险：使用 dde-am 执行命令

  • 变更内容：

    fix: Use dde-am to execute command in notifications
    

  • 逻辑分析：结合上述的 Revert，这里将通知中的命令执行改为了通过 dde-am（可能是 DDE Application Manager 或类似的中间件）来执行。
  • 建议：需要确保 dde-am 能够正确处理不可信输入，并且不会因为上述白名单的移除而成为攻击向量。

2. 代码质量与兼容性审查

• 枚举顺序调整

  • 变更内容：

    feat: reorder task manager role enum for compatibility
    fix: move CategoriesRole to end of enum for compatibility
    

  • 分析：调整枚举顺序通常是为了保持二进制兼容性（ABI）。
  • 建议：
    • 这是一个好的实践，特别是在 C++ 或 QML 绑定中，向枚举末尾添加新值或调整顺序以避免破坏现有索引。
    • 后续检查：建议检查代码中是否有硬编码的数值索引依赖于旧的枚举顺序，虽然这属于代码质量较差的表现，但重构时需要留意。

• 动画与解耦

  • 变更内容：

    fix: refactor dock position management and decouple from animation flow
    fix: disable dock animations during resize operations
    

  • 分析：将逻辑与动画解耦，并在特定操作（Resize）期间禁用动画，是提升用户体验和性能的常见做法。
  • 建议：这属于代码架构优化，有助于减少 UI 卡顿和逻辑混乱，值得肯定。

3. 文档规范审查

• 时间戳异常

  • 内容：Thu, 29 Jan 2026 20:22:15 +0800
  • 问题：年份显示为 2026 年。
  • 建议：请确认这是否为笔误（应为 2024 或 2025）。错误的年份可能会影响自动打包工具或版本排序逻辑。

• 格式规范

  • 内容：整体遵循了 Debian changelog 的标准格式（package (version) distribution; urgency）。
  • 建议：格式规范，但在描述回退时，如果空间允许，简要注明回退的原因会更有利于后续维护（例如：Revert "..." due to compatibility issues）。

总结建议

1. 首要任务：确认关于通知白名单回退的安全性。这是本次变更中最大的潜在风险点。
2. 修正错误：将 changelog 中的年份 2026 修正为实际年份。
3. 代码审查配合：在审查具体代码实现时，重点关注 dde-am 的调用链路以及枚举变更对现有代码的影响。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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)

[deepin-bot]

TAG Bot

✅ Tag created successfully

📋 Tag Details

• Tag Name: 2.0.28
• Tag SHA: 85af00002716799bf74cb09dd67ce2e148ecbb32
• Commit SHA: fca7336f68a3a6b8c95ae396ea8ad16a519a0b6d
• Tag Message:

  Release dde-shell 2.0.28
  
  

• Tagger:
  • Name: mhduiy
• Distribution: unstable