Skip to content

fix: update version to 6.0.48#378

Merged
lzwind merged 1 commit intolinuxdeepin:masterfrom
JWWTSL:master
Dec 5, 2025
Merged

fix: update version to 6.0.48#378
lzwind merged 1 commit intolinuxdeepin:masterfrom
JWWTSL:master

Conversation

@JWWTSL
Copy link
Contributor

@JWWTSL JWWTSL commented Dec 5, 2025

log: update version.

Summary by Sourcery

Bump deepin-album package metadata to version 6.0.48.1 across all architectures and packaging files.

Build:

  • Update linglong packaging manifests for all architectures to reference version 6.0.48.1.

Chores:

  • Refresh Debian packaging changelog for the 6.0.48.1 release.

log: update version.
@github-actions
Copy link

github-actions bot commented Dec 5, 2025

TAG Bot

TAG: 6.0.48
EXISTED: no
DISTRIBUTION: unstable

@sourcery-ai
Copy link

sourcery-ai bot commented Dec 5, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR bumps the deepin-album package version from 6.0.47.1 to 6.0.48.1 across all architecture-specific linglong manifests and prepares the Debian changelog for a new entry.

File-Level Changes

Change Details Files
Update application package version in all Linglong manifests for each architecture.
  • Change package.version from 6.0.47.1 to 6.0.48.1 in the root Linglong manifest
  • Change package.version from 6.0.47.1 to 6.0.48.1 in the arm64 Linglong manifest
  • Change package.version from 6.0.47.1 to 6.0.48.1 in the loong64 Linglong manifest
  • Change package.version from 6.0.47.1 to 6.0.48.1 in the sw64 Linglong manifest
linglong.yaml
arm64/linglong.yaml
loong64/linglong.yaml
sw64/linglong.yaml
Start updating Debian packaging metadata for the new release version.
  • Modify debian/changelog to begin a new entry for version 6.0.48.x (exact content not shown in snippet)
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

@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 there - I've reviewed your changes - here's some feedback:

  • Since the version is duplicated across multiple architecture-specific linglong.yaml files, consider centralizing the version definition (or using a shared template/mechanism) to reduce the chance of inconsistent bumps in future releases.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Since the version is duplicated across multiple architecture-specific linglong.yaml files, consider centralizing the version definition (or using a shared template/mechanism) to reduce the chance of inconsistent bumps in future releases.

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

deepin pr auto review

我来对这个diff进行审查:

  1. 语法逻辑:
  • 所有文件中的版本号更新语法正确,格式统一
  • changelog条目格式符合Debian标准
  1. 代码质量:
  • 所有架构的linglong.yaml文件都同步更新了版本号,保持了一致性
  • changelog中的变更记录简洁明了
  1. 代码性能:
  • 这些是配置文件的修改,不会影响程序运行性能
  1. 代码安全:
  • 版本号更新本身不涉及安全问题

改进建议:

  1. changelog中的变更记录过于简单:
-  * fix bug.
+  * Fix image loading issue in specific formats

建议使用更具体的bug描述,这样更容易追踪和回溯问题。

  1. 版本号管理:
    当前版本号是 6.0.48.1,建议考虑使用语义化版本控制(SemVer),并确保:
  • 主版本号:不兼容的API修改
  • 次版本号:向下兼容的功能性新增
  • 修订号:向下兼容的问题修正
  1. 建议添加变更类型标签:
+deepin-album (6.0.48) unstable; urgency=medium
+
+  * [Fix] Fix image loading issue in specific formats
+
+ -- Tian ShiLin <tianshilin@uniontech.com>  Fri, 05 Dec 2025 13:53:12 +0800

使用[Fix]、[Feat]、[Docs]等标签可以更清晰地标识变更类型。

  1. 建议在所有linglong.yaml文件中添加更新说明注释:
package:
  id: org.deepin.album
  name: deepin-album
  version: 6.0.48.1  # Updated to fix image loading issue

这些改进可以让版本管理和变更追踪更加清晰和专业。

@deepin-ci-robot
Copy link

[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

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