chore: bump version to 1.1.72

[yixinshark]

update changelog to 1.1.72

Summary by Sourcery

Chores:

• Update Debian changelog entries to reflect version 1.1.72.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Debian packaging metadata to reflect release version 1.1.72.

File-Level Changes

Change	Details	Files
Update Debian changelog entry for new release version 1.1.72.	Adjust changelog header/version to 1.1.72 for the latest release. Update associated metadata fields in the changelog entry (e.g., date, maintainer, or notes) to match the new release, if present.	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: 1.1.72
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]

deepin pr auto review

我来对这个git diff进行审查：

1. 语法逻辑：

• changelog的格式符合Debian的规范，包含了版本号、发布状态、紧急程度
• 变更条目使用了标准的"*"符号标记
• 维护者信息和日期格式正确

2. 代码质量：

• 变更描述简洁明了
• 两个修复项都有明确的说明：
  • "fix: initialize member variables to prevent undefined behavior" - 修复了成员变量初始化问题
  • "fix: remove de_CH resource" - 移除了不需要的资源
• 版本号从1.1.71递增到1.1.72，符合语义化版本控制

3. 代码性能：

• 虽然这是changelog文件，但从描述的变更来看：
  • 初始化成员变量可以防止未定义行为，提高程序稳定性
  • 移除不必要的资源可以减小程序体积

4. 代码安全：

• 初始化成员变量是一个好的安全实践，可以防止使用未初始化的变量导致的安全漏洞
• 移除不需要的资源可以减少潜在的攻击面

改进建议：

1. changelog本身没有明显问题，但建议：

   • 可以考虑在变更描述中添加更多上下文信息
   • 如果这些修复是针对特定的bug报告，可以添加相关的bug编号

2. 对于实际的代码变更：

   • 建议确保所有成员变量都在构造函数初始化列表中进行初始化
   • 移除资源时，建议检查是否有其他代码依赖这些资源

3. 版本管理：

   • 建议在发布前进行完整的回归测试
   • 考虑在变更日志中添加影响范围说明

总的来说，这是一个规范的changelog变更，描述清晰，版本管理合理。

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wjyrich, yixinshark

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