chore: bump version to 1.0.17

[fly602]

update changelog to 1.0.17

Summary by Sourcery

Bump the package version to 1.0.17 in the Debian changelog.

[github-actions]

TAG Bot

TAG: 1.0.17
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

deepin pr auto review

我来对这个 changelog 的变更进行审查：

1. 版本号和格式：

• 版本号从 1.0.16 升级到 1.0.17，符合语义化版本规范
• changelog 格式符合 Debian 标准，包含了版本号、发行版（unstable）和紧急程度（medium）

2. 变更内容分析：

a) chore: remove OOMScoreAdjust plugin

• 这是一个维护性变更，移除了 OOMScoreAdjust 插件
• 建议补充说明移除原因，比如是否已不再需要或被其他方案替代

b) fix: remove unnecessary dependencies from xsettings service

• 修复类变更，移除了不必要的依赖
• 建议具体说明移除了哪些依赖，以及为什么这些依赖是不必要的

c) feat: refactor ipwatchd plugin to use service group framework

• 这是一个功能性变更，重构了 ipwatchd 插件
• 建议说明使用服务组框架的好处，比如是否提高了性能或可维护性

d) refactor: convert xsettings from executable to plugin

• 这是一个重构变更，将 xsettings 从可执行文件转换为插件
• 注意这个变更与 1.0.16 版本中的 "convert xsettings from plugin to standalone application" 相反
• 建议在变更说明中解释这次反转的原因，以及为什么插件形式更适合

3. 改进建议：

1. 变更描述应该更详细：

• 每个变更都应该包含足够的上下文信息
• 特别是对于重构类的变更，应该说明重构的原因和带来的好处

2. 变更类型使用建议：

• 目前使用了 chore、fix、feat 和 refactor，类型选择合理
• 建议保持这种规范化的变更类型使用

3. 版本变更的连贯性：

• 1.0.16 和 1.0.17 中对 xsettings 的处理是相反的
• 建议在变更说明中更清楚地解释这种变更的原因

4. 时间戳：

• 时间戳显示为 2025 年 12 月 19 日，这似乎是一个未来的日期
• 建议使用正确的提交时间

5. 建议添加 Breaking Changes 标记：

• 如果某些变更可能会影响现有功能，建议明确标记

总结：
这个 changelog 的基本格式是正确的，但变更描述可以更加详细和清晰。特别是对于 xsettings 的处理方式的变更，需要更详细的说明。建议在后续的 changelog 维护中：

1. 提供更详细的变更说明
2. 解释重要变更的原因
3. 确保时间戳的准确性
4. 对于可能影响用户的变更，提供额外的说明

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Version bump to 1.0.17 with corresponding Debian changelog update stubbed but diff contents not provided.

File-Level Changes

Change	Details	Files
Prepare Debian packaging metadata for release 1.0.17.	Update the Debian changelog entry to reference version 1.0.17. Ensure packaging version metadata aligns with 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]

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

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

[fly602]

/forcemerge

[deepin-bot]

This pr force merged! (status: blocked)