Skip to content

chore: Update linglong base and runtime#273

Merged
lzwind merged 1 commit into
linuxdeepin:develop/snipefrom
wangrong1069:pr0917
Sep 17, 2025
Merged

chore: Update linglong base and runtime#273
lzwind merged 1 commit into
linuxdeepin:develop/snipefrom
wangrong1069:pr0917

Conversation

@wangrong1069
Copy link
Copy Markdown
Contributor

@wangrong1069 wangrong1069 commented Sep 17, 2025

Update linglong base and runtime

Log: Update linglong base and runtime

Summary by Sourcery

Bump dde-calendar package version and update linglong packaging to use latest base and runtime dependencies

Enhancements:

  • Bump dde-calendar package version to 6.5.22.1
  • Update linglong base to org.deepin.base/25.2.1 for arm64, x86_64, and loong64
  • Update linglong runtime to org.deepin.runtime.dtk/25.2.1 for arm64, x86_64, and loong64

Documentation:

  • Update Debian changelog to reflect new package version

Update linglong base and runtime

Log: Update linglong base and runtime
@github-actions
Copy link
Copy Markdown

TAG Bot

TAG: 6.5.22
EXISTED: no
DISTRIBUTION: unstable

@deepin-ci-robot
Copy link
Copy Markdown

deepin pr auto review

根据提供的git diff,我将对这个更新进行审查:

  1. 版本更新:
  • 应用版本从6.5.21.1更新到6.5.22.1
  • 基础镜像(base)和运行时(runtime)版本从25.2.0更新到25.2.1
  • 这个更新涉及了多个架构平台(arm64、x86_64、loong64)
  1. 代码质量评估:
  • 版本号格式保持一致,遵循了语义化版本规范
  • changelog记录规范,包含了必要的更新说明和作者信息
  • 多平台架构的更新保持同步,确保一致性
  1. 改进建议:
  • 建议在changelog中添加更详细的更新内容说明,而不仅仅是"Update linglong base and runtime"
  • 考虑添加更新原因的说明,例如为什么需要升级base和runtime版本
  • 建议在更新base和runtime版本时,检查是否有相关的依赖更新需要同步进行
  1. 安全性考虑:
  • base和runtime的更新通常包含安全补丁,这是一个好的实践
  • 建议确认新版本的base和runtime是否包含任何已知的安全修复
  1. 性能影响:
  • base和runtime的更新可能会带来性能改进
  • 建议在后续版本中添加性能测试结果,以验证更新是否带来了预期的性能提升

总体而言,这是一个常规的版本更新,主要关注基础组件的升级。建议在更新后进行充分的测试,确保应用在新版本的base和runtime上能够正常工作。

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

  • Consider centralizing the base and runtime version values in a shared template or variable so you don’t have to manually update each architecture-specific YAML.
  • You could add a small script or Makefile target to automate version bumps across all YAML files and reduce repetitive manual edits.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider centralizing the base and runtime version values in a shared template or variable so you don’t have to manually update each architecture-specific YAML.
- You could add a small script or Makefile target to automate version bumps across all YAML files and reduce repetitive manual edits.

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.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Sep 17, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the dde-calendar package manifests by bumping the application version to 6.5.22.1 and upgrading base/runtime dependencies to 25.2.1 across all architectures, and adds a corresponding entry in the Debian changelog.

File-Level Changes

Change Details Files
Bump application version to 6.5.22.1
  • Updated version field in each manifest from 6.5.21.1 to 6.5.22.1
arm64/linglong.yaml
linglong.yaml
loong64/linglong.yaml
Upgrade base and runtime dependencies to 25.2.1
  • Updated base reference from 25.2.0 to 25.2.1
  • Updated runtime reference from 25.2.0 to 25.2.1
arm64/linglong.yaml
linglong.yaml
loong64/linglong.yaml
Refresh Debian changelog
  • Added or updated entry for version 6.5.22.1
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

@lzwind lzwind merged commit f4af9ac into linuxdeepin:develop/snipe Sep 17, 2025
22 checks passed
@deepin-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@wangrong1069 wangrong1069 deleted the pr0917 branch September 17, 2025 06:02
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