Skip to content

fix: update version to 6.5.38#200

Merged
lzwind merged 1 commit into
linuxdeepin:masterfrom
JWWTSL:master
May 28, 2026
Merged

fix: update version to 6.5.38#200
lzwind merged 1 commit into
linuxdeepin:masterfrom
JWWTSL:master

Conversation

@JWWTSL

@JWWTSL JWWTSL commented May 28, 2026

Copy link
Copy Markdown
Contributor

log: update version.

Summary by Sourcery

Bump the application package version metadata to 6.5.39.1.

Enhancements:

  • Update packaging configuration to reflect the new 6.5.39.1 release version.

Build:

  • Adjust package version in linglong.yaml for the new release.

log: update version.
@github-actions

Copy link
Copy Markdown

TAG Bot

TAG: 6.5.39
EXISTED: no
DISTRIBUTION: unstable

@sourcery-ai

sourcery-ai Bot commented May 28, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR bumps the application package version from 6.5.38.1 to 6.5.39.1 in the Linglong packaging metadata, aligning it with the intended 6.5.38 release note wording (likely a typo in the title/description).

File-Level Changes

Change Details Files
Update application package version metadata to new release version.
  • Change package.version value in the Linglong manifest from 6.5.38.1 to 6.5.39.1
linglong.yaml

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • The PR title and description mention version 6.5.38, but the actual change bumps to 6.5.39.1; please align the metadata so the version you’re releasing is consistently referenced.
  • Consider checking for other version declarations in the repository (e.g., additional config or packaging files) to ensure they are all updated to 6.5.39.1 for consistency.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The PR title and description mention version 6.5.38, but the actual change bumps to 6.5.39.1; please align the metadata so the version you’re releasing is consistently referenced.
- Consider checking for other version declarations in the repository (e.g., additional config or packaging files) to ensure they are all updated to 6.5.39.1 for consistency.

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 输入。本次提交主要涉及项目版本的升级(从 6.5.38 升级至 6.5.39),修改了 debian/changeloglinglong.yaml 两个文件。

以下是针对本次代码变更的审查意见:

1. 语法逻辑

  • Debian Changelog 格式:新增的 changelog 条目基本符合 Debian Changelog 的标准格式(包含包名、版本号、发行版、紧急程度、描述、维护者姓名邮箱、时间戳)。
  • Linglong YAML 格式:YAML 文件中的版本号字符串修改语法正确,没有引入缩进或格式错误。
  • 逻辑一致性debian/changelog 中的版本号为 6.5.39,而 linglong.yaml 中的版本号为 6.5.39.1。虽然两者后缀不同(通常 linglong 的版本号会多一位构建号或补丁号),但在项目版本迭代的逻辑上是合理的,保持了一致的升级趋势。

2. 代码质量

  • 描述规范性debian/changelog 中的更新描述为 * update version to 6.5.39.。在高质量的开源项目维护中,changelog 应当记录本次版本包含的实质性功能修改或 Bug 修复,而不仅仅是记录“更新了版本号”。版本号的变更本身已经体现了版本的更新。
    • 改进建议:建议在此处补充本次版本迭代实际包含的代码变更说明,例如:* feat: add new font preview feature* fix: crash on startup under wayland。如果这只是一个纯粹的版本发布准备提交,建议将之前未记录的修改汇总在此。

3. 代码性能

  • 无影响:本次修改仅涉及元数据文件和构建配置文件,不涉及任何业务逻辑代码的变更,因此对程序的运行时性能没有任何影响。

4. 代码安全

  • 时间戳异常(潜在风险)debian/changelog 中的时间戳为 Thu, 28 May 2026 19:59:59 +0800。这个日期位于未来(2026年)
    • 风险分析:在正常的开发流程中,使用未来时间可能是由于系统时钟错误,或者是为了绕过某些构建系统的版本时间校验。但在正式的包管理系统中,包的时间戳如果出现逻辑混乱(早于实际构建时间或依赖包的时间),可能会导致 APT 或其他包管理器在处理依赖和版本升级时出现不可预知的排序或覆盖问题。
    • 改进建议:请确认该时间戳是否为笔误或系统时钟导致。建议使用真实的当前时间(可通过 dch 命令自动生成正确的时间戳)。

总结

本次 Diff 是一次标准的版本号更新提交,整体格式规范。但建议关注以下两点:

  1. 修正 changelog 中的未来时间戳,确保构建系统的时序逻辑正常。
  2. 完善 changelog 的修改描述,使其真正反映本次版本迭代的实际代码变更,便于后续追溯和维护。

@deepin-ci-robot

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: JWWTSL, lzwind

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

@lzwind lzwind merged commit da65418 into linuxdeepin:master May 28, 2026
18 of 20 checks passed
@deepin-bot

deepin-bot Bot commented May 28, 2026

Copy link
Copy Markdown
Contributor

TAG Bot

Tag created successfully

📋 Tag Details
  • Tag Name: 6.5.39
  • Tag SHA: 494ef3ddbc6b137fb6ae22dd747f7a5a844d8ce1
  • Commit SHA: da65418d51294301d8afde999292322c71fe6a06
  • Tag Message:
    Release deepin-font-manager 6.5.39
    
    
  • Tagger:
    • Name: JWWTSL
  • 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.

3 participants