Skip to content

chore: bump version to 6.0.36#312

Merged
deepin-bot[bot] merged 1 commit into
linuxdeepin:masterfrom
Johnson-zs:master
May 28, 2026
Merged

chore: bump version to 6.0.36#312
deepin-bot[bot] merged 1 commit into
linuxdeepin:masterfrom
Johnson-zs:master

Conversation

@Johnson-zs
Copy link
Copy Markdown
Contributor

@Johnson-zs Johnson-zs commented May 28, 2026

6.0.36

Log:

Summary by Sourcery

Chores:

  • Update Debian packaging metadata to reflect version 6.0.36.

@deepin-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Johnson-zs

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions
Copy link
Copy Markdown

TAG Bot

TAG: 6.0.36
EXISTED: no
DISTRIBUTION: unstable

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 28, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Bumps the project/package version to 6.0.36 in the Debian packaging metadata.

File-Level Changes

Change Details Files
Update Debian packaging metadata to reflect version 6.0.36.
  • Increment the recorded package version to 6.0.36 in the Debian changelog.
  • Ensure the top changelog entry corresponds to 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

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@deepin-ci-robot
Copy link
Copy Markdown

deepin pr auto review

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

本次提交是一个 Debian 变更日志的更新,主要记录了 dde-grand-search 版本从 6.0.35 升级到 6.0.36 的修改内容。由于这仅涉及打包和发布元数据的修改,而非业务逻辑代码,因此不存在传统意义上的语法逻辑、代码性能和代码安全漏洞问题

不过,从代码质量、规范性和发布管理的角度来看,仍有以下几点改进意见:

1. 代码质量与规范性

  • 日期格式存在潜在问题
    你的日期格式为 Thu, 28 May 2026 19:48:46 +0800。Debian 变更日志对日期格式有极其严格的要求,必须符合 RFC 2822 格式(即 Day-of-week, DD Mon YYYY HH:MM:SS +ZONE)。

    • 问题:2026年5月28日是星期四,你的填写是正确的。但如果你是使用脚本或手动修改日期,请务必确保星期几与年月日是严格对应的。如果日期与星期不匹配,dpkg-buildpackage 等打包工具可能会报错或产生警告。
    • 建议:建议使用 date -R 命令自动生成当前时间的 RFC 2822 格式字符串,以避免人为计算星期导致的错误。
  • Changelog 条目粒度与分类
    目前的条目包含了新功能、重构和杂项:

    • feat: optimize search UI icons and layout spacing
    • feat: refactor search result display with fixed modification time
    • chore: update translations
    • refactor: migrate icons to theme-based system with DTK
    • 建议:第二条 feat 中包含了 refactor 的语义,这容易造成分类混淆。建议将功能新增与代码重构分开描述。例如:
      • feat: display fixed modification time in search results
      • refactor: optimize search UI icons, layout spacing and migrate to DTK theme-based system

2. 语法逻辑

  • 空行规范
    在 Debian Changelog 中,最新版本的条目与上一版本条目之间保留空行是正确的(如你 diff 中所示),这符合 Debian Changelog 的语法解析逻辑,无需修改。

3. 代码性能与代码安全

  • 不适用debian/changelog 是纯文本的发布日志文件,不参与程序的编译期优化或运行期执行,因此不存在性能损耗和安全风险。
  • 隐私提示:提交者信息 Zhang Sheng <zhangsheng@uniontech.com> 属于开发者公开信息,不涉及敏感数据泄露。

总结

这是一个非常标准的 Debian 打包提交。主要的改进点在于规范 Changelog 的描述语义,并确保日期生成的自动化与准确性。如果你在后续提交中包含了 C++/Qt 的业务代码(如 DTK 重构或搜索逻辑修改),欢迎再次提交 Diff,我将为你进行深度的代码逻辑、性能与安全审查!

@Johnson-zs
Copy link
Copy Markdown
Contributor Author

/forcemerge

@deepin-bot
Copy link
Copy Markdown

deepin-bot Bot commented May 28, 2026

This pr force merged! (status: blocked)

@deepin-bot deepin-bot Bot merged commit 3c0b4c8 into linuxdeepin:master May 28, 2026
10 of 12 checks passed
@deepin-bot
Copy link
Copy Markdown

deepin-bot Bot commented May 28, 2026

TAG Bot

Tag created successfully

📋 Tag Details
  • Tag Name: 6.0.36
  • Tag SHA: c484971fc5b3cfe7c4aade99be1e1847d48d23ad
  • Commit SHA: 3c0b4c85c932e11c516e66d8809a1c6cdac8bf82
  • Tag Message:
    Release dde-grand-search 6.0.36
    
    
  • Tagger:
    • Name: Johnson-zs
  • Distribution: unstable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants