chore: bump version to 6.1.56

[18202781743]

update changelog to 6.1.56

Summary by Sourcery

Bump package version to 6.1.56 and update the Debian changelog accordingly.

Chores:

• Bump version to 6.1.56
• Update Debian changelog for version 6.1.56

[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 6.1.56.

File-Level Changes

Change	Details	Files
Bump project version to 6.1.56 in Debian changelog	Replace previous version number with 6.1.56 Update the release date and timestamp Refresh changelog entry header for the new 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.

[github-actions]

TAG Bot

TAG: 6.1.56
EXISTED: no
DISTRIBUTION: unstable

[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: 18202781743, robertkill

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

[deepin-ci-robot]

deepin pr auto review

根据提供的git diff内容，我看到这是dde-daemon包的changelog变更记录。以下是我的审查意见：

1. 代码逻辑方面：

• 变更记录显示了一系列功能重构和修复，从自定义配置助手迁移到dconfig模块，这是良好的架构改进
• 多屏场景下的合盖处理和触摸板禁用修复显示了系统交互逻辑的完善
• 密码认证修复解决了系统唤醒时的安全性问题

2. 代码质量方面：

• 变更记录格式规范，遵循了Debian changelog的标准格式
• 提交信息清晰明了，每个变更都有明确的标识（refactor/feat/fix/chore）
• 变更描述简洁但信息完整，便于理解和追踪

3. 代码性能方面：

• 从gsettings和GSettings迁移到DConfig可能会带来性能提升，因为DConfig可能是针对系统优化的配置管理方案
• 移除GNOME包装器配置可能减少了不必要的系统开销

4. 代码安全方面：

• 密码认证修复增强了系统安全性
• 配置系统的重构可能提高了配置管理的安全性

建议改进：

1. 对于配置迁移相关的变更（如从gsettings到dconfig），建议在变更记录中简要说明迁移的原因和预期收益，这将有助于其他开发者理解变更的必要性
2. 对于"touchpad cannot be properly disabled"这样的修复，建议在变更记录中更详细地描述问题现象和修复方案，便于后续问题排查
3. 建议在提交信息中包含相关的issue编号或bug跟踪号，这样可以更好地追踪问题解决过程
4. 对于多屏场景的改进，建议补充测试用例说明，确保修复的完整性

总体而言，这些变更看起来是积极和必要的，有助于提高系统的稳定性、性能和用户体验。