chore: update changelog to 1.0.25

[mhduiy]

更新说明

自动更新 changelog 到版本 1.0.25

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

• Bump recorded package version to 1.0.25 in debian/changelog.

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mhduiy

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

[github-actions]

TAG Bot

TAG: 1.0.25
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Debian packaging changelog to reflect the new release version 1.0.25 targeting master, with no code or behavior changes.

File-Level Changes

Change	Details	Files
Align Debian packaging changelog with new release version 1.0.25.	Add or update a changelog entry for version 1.0.25 in the Debian changelog. Ensure release metadata (version and possibly date/maintainer entry) is consistent with the master branch target.	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.}

[mhduiy]

/forcemerge

[deepin-bot]

This pr force merged! (status: blocked)

[deepin-bot]

TAG Bot

✅ Tag created successfully

📋 Tag Details

• Tag Name: 1.0.25
• Tag SHA: 2774eadabf8d8b063455e3566d7eba230e775af4
• Commit SHA: a754ef445c7d7ed9ea3676fc14aded163f4237cd
• Tag Message:

  Release dde-services 1.0.25
  
  

• Tagger:
  • Name: mhduiy
• Distribution: unstable

[deepin-ci-robot]

deepin pr auto review

你好！我是CodeGeeX。我已仔细审查了你提供的 Git Diff 内容。

本次提交主要修改了 debian/changelog 文件，记录了 dde-services (1.0.25) 版本的变更。从提交信息来看，本次优化的核心是针对 XSettings1 启动性能的提升，具体措施包括：移除 Before 约束、跳过冗余初始化以及清理调试代码。

由于本次 Diff 仅包含 debian/changelog 的变更，未包含实际的代码改动，我无法直接对语法逻辑、代码性能和代码安全进行深度的代码级审查。不过，基于你提交信息中提到的三个优化方向，我将为你提供详细的改进建议和潜在风险点分析，供你在审查或编写实际代码时参考：

1. 移除 Before 约束

• 潜在风险（逻辑与安全）：在 Systemd 单元文件中，Before 和 After 用于控制服务的启动顺序。移除 Before 约束虽然能减少等待时间、加快启动速度，但必须确保 XSettings1 没有必须在其他特定服务之前启动的硬性依赖。如果依赖关系处理不当，可能会导致其他服务在读取 XSettings 配置时获取到空值或默认值，从而引发图形界面显示异常或逻辑错误。
• 改进意见：
  • 请确认原本被 Before 约束的服务是否真的不需要依赖 XSettings1。
  • 如果只是想优化启动并发度，可以考虑将强依赖改为弱依赖（如 WantedBy 或使用 After 而非 Before），或者通过 D-Bus 激活机制来替代静态的启动顺序约束。

2. 跳过冗余初始化

• 潜在风险（逻辑与性能）：所谓的“冗余”是否真的冗余？在某些情况下，看似冗余的初始化可能是为了处理服务重启、崩溃恢复或配置文件热更新后的状态重置。如果盲目跳过，可能会导致状态不一致。
• 改进意见：
  • 确保跳过初始化的逻辑有明确的状态检查（例如：检查共享内存是否已存在、D-Bus 名称是否已注册、配置文件哈希是否改变等）。
  • 建议在代码中添加清晰的注释，说明为何该初始化是冗余的，以及在什么条件下可以安全跳过，避免后续维护者误将其当作 Bug 修复回来。

3. 清理调试代码

• 潜在风险（安全与性能）：调试代码（如 qDebug, printf, 详细的日志输出）如果遗留在生产环境中，不仅会拖慢性能（I/O 阻塞），还可能泄露敏感信息（如用户路径、配置细节等）。
• 改进意见：
  • 确保清理的是纯粹的开发期调试代码，而不是异常处理分支中的关键日志。
  • 对于必须保留的日志，建议使用日志级别控制（如 Qt 的 qCInfo / qCDebug 分类），并在发布版本中默认关闭 Debug 级别的输出，而不是直接删除日志语句，这样在排查线上问题时可以通过环境变量重新开启。
  • 检查是否清理了临时的后门代码或硬编码的测试路径，确保代码安全。

4. 关于 Changelog 格式规范

• 格式规范：当前 Changelog 格式符合 Debian 规范，但日期格式 Fri, 15 May 2026 09:35:57 +0800 中的年份是 2026年。虽然这可能是你手动测试 dch 时的系统时间问题，但请注意在正式打包发布前修正为当前真实日期，以免引起版本管理混乱。

---

总结：
你的优化方向非常明确，针对启动耗时的痛点进行了有效打击。为了让我能够进行更深入的代码级审查（如语法逻辑、内存安全、并发竞争等），请提供涉及本次修改的 .service 文件、C/C++ 或 Python 源代码的 Diff 内容。我将很乐意为你提供更详尽的代码审查服务！