chore: update changelog to 2.0.90

[mhduiy]

更新说明

自动更新 changelog 到版本 2.0.90

变更内容

• 更新 debian/changelog

版本信息

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

Summary by Sourcery

Chores:

• Refresh debian/changelog entries to reflect version 2.0.90.

[github-actions]

TAG Bot

TAG: 2.0.90
EXISTED: no
DISTRIBUTION: unstable

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the Debian changelog to bump the package version to 2.0.90 on the master branch, with no functional code changes.

File-Level Changes

Change	Details	Files
Bump Debian package changelog entry to version 2.0.90.	Add or update the topmost changelog stanza to reflect version 2.0.90. Adjust associated metadata in the changelog entry (e.g., date, maintainer, and description) to document the new release. Ensure the target distribution/branch information in the changelog aligns with master.	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.

[deepin-ci-robot]

deepin pr auto review

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

本次提交是一个 Debian changelog 文件的更新，版本号从 2.0.89 升级到了 2.0.90，主要记录了多个 Bug 修复。

由于本次 Diff 仅涉及 debian/changelog（属于打包和发布说明文件），不包含实际的程序代码（如 C++/Go/Python 等），因此我无法针对语法逻辑、代码性能和代码安全进行直接评估。

不过，针对这份 Changelog 的编写规范和其中透露出的代码逻辑线索，我提供以下审查意见和改进建议：

1. 格式与规范审查

Debian Changelog 有着严格的格式要求（通常由 debhelper 或 dch 工具生成），你的格式大体正确，但有以下细节需要注意：

• 日期格式问题（潜在风险）：
  日期部分写的是 Wed, 20 May 2026 15:16:51 +0800。2026年是一个未来的时间。在 Debian 打包规范中，changelog 的时间通常应为当前真实时间。如果时间设置在未来，可能会导致 dpkg 打包时出现警告，甚至在某些 CI/CD 流程或依赖解析时出现不可预期的排序错误。建议确认是否为笔误，若是请修正为当前时间。
• 条目描述规范：
  每行描述前有两个空格，条目以星号 * 开头，这是符合规范的。但注意第6-7行：

  * fix: resolve potential crash and resource management issues in
    network module
  

  第二行的缩进应该与上一行的文本对齐（即星号后有两个空格，共3个字符的缩进），当前看起来是一个空格加换行，虽然不影响编译，但不符合最佳排版美学。建议改为：

  * fix: resolve potential crash and resource management issues in
    network module
  

  （确保 network 前面有3个空格与 resolve 对齐）。

2. 从 Changelog 逻辑反推代码质量的改进建议

虽然看不到代码，但从这些 fix 记录中，我们可以反推出之前代码存在的一些架构和设计问题，建议在实际代码库中进行相应的排查和重构：

• fix: use loose regex for IP and mask input
  • 逻辑与安全建议：放宽（loose）正则表达式虽然能解决用户输入被误拦截的问题，但也可能引入新的安全风险。IP 地址和子网掩码的校验如果过于宽松，可能导致后端程序解析异常或引发网络配置错误。建议检查实际代码中的正则，确保在“宽松”的同时，依然排除了非法字符（如字母、非法符号）和明显越界的值（如 256以上的数字）。
• fix: resolve potential crash and resource management issues in network module
  • 性能与安全建议：“潜在崩溃和资源管理问题”通常意味着存在内存泄漏、野指针或并发竞争。既然修复了，建议审查修复的方式：
    1. 如果是 C++ 代码，是否全面使用了智能指针（std::unique_ptr, std::shared_ptr）来替代裸指针？
    2. 如果涉及异步网络请求或 DBus 通信，是否正确使用了生命周期安全的回调机制（如 std::weak_ptr 捕获）来防止悬垂回调？
• fix: enforce baseLayer focus when launcher becomes visible
  • 逻辑建议：强制聚焦有时只是掩盖了焦点管理混乱的表象。建议检查 UI 框架的事件循环，确保组件显隐时的焦点转移逻辑是自然且符合框架设计的，而非依赖强制 focus() 调用。
• fix: fix wired connection name showing English on Chinese locale
  • 逻辑建议：国际化（i18n）翻译失效通常是因为翻译键值缺失，或者是在代码中硬编码了字符串。建议排查其他网络相关的字符串是否也存在硬编码问题，确保全部走翻译流（如 tr() 或 gettext）。

总结

这份 Changelog 本身没有严重问题，只需注意修正可能的时间穿越问题（2026年）和微调换行对齐。

如果你希望我对上述 fix 涉及的实际代码逻辑、性能或安全性进行深度审查，请提供对应的代码 Diff（例如 .cpp, .h, .go 等文件的修改），我将为你提供详细的代码级审查意见！

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

[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

[deepin-bot]

TAG Bot

✅ Tag created successfully

📋 Tag Details

• Tag Name: 2.0.90
• Tag SHA: fc989c38f338a05dc577fa3ed11bfc0ec38a7430
• Commit SHA: 274ebde0a07b453e96a7afd36d490556049ca205
• Tag Message:

  Release dde-network-core 2.0.90
  
  

• Tagger:
  • Name: mhduiy
• Distribution: unstable