Skip to content

Release 6.7.51 - #589

Merged
deepin-bot[bot] merged 1 commit into
masterfrom
release-6.7.51
Oct 15, 2026
Merged

deepin-bot[bot] merged 1 commit into
masterfrom
release-6.7.51

Conversation

@deepin-bot

@deepin-bot deepin-bot Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

6.7.51 - 2026-10-15


This PR is triggered by @18202781743

Summary by Sourcery

Release version 6.7.51 and synchronize project and packaging metadata.

Build:

  • Update package metadata for the 6.7.51 release across Arch Linux and RPM packaging.

Documentation:

  • Add the 6.7.51 entry to the changelog.

Chores:

  • Bump the project version from 6.7.50 to 6.7.51.

@sourcery-ai

sourcery-ai Bot commented Oct 15, 2026

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

Reviewer's Guide

This release-only PR increments dtkcore from 6.7.50 to 6.7.51 and synchronizes the version across changelog, canonical metadata, and Arch Linux/RPM/Debian packaging files; it contains no functional code changes.

File-Level Changes

Change Details Files
Bump the project release version across source metadata and packaging definitions.
  • Add the 6.7.51 release heading and date to the changelog.
  • Update the canonical version and Debian changelog metadata.
  • Synchronize Arch Linux and RPM package versions to 6.7.51.
CHANGELOG.md
VERSION
archlinux/PKGBUILD
debian/changelog
rpm/dtkcore.spec

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

@deepin-ci-robot

Copy link
Copy Markdown
Contributor

Hi @deepin-bot[bot]. Thanks for your PR.

I'm waiting for a linuxdeepin member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@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 found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="CHANGELOG.md" line_range="8" />
<code_context>
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

+## [6.7.51] - 2026-10-15
+
 ## [6.7.50] - 2026-09-22
</code_context>
<issue_to_address>
**Release comparison link is missing**

When readers use the changelog expecting the comparison link shown in the PR description, the new heading has no corresponding comparison-link definition in `CHANGELOG.md`, so Markdown renders `[6.7.51]` as unlinked text and readers cannot open the release comparison.

Add the 6.7.51 comparison-link reference to `CHANGELOG.md`.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread CHANGELOG.md
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [6.7.51] - 2026-10-15

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚪ Low · Release comparison link is missing

When readers use the changelog expecting the comparison link shown in the PR description, the new heading has no corresponding comparison-link definition in CHANGELOG.md, so Markdown renders [6.7.51] as unlinked text and readers cannot open the release comparison.

Add the 6.7.51 comparison-link reference to CHANGELOG.md.

Prompt for AI agents
In `CHANGELOG.md` at line 8:

**Release comparison link is missing**

When readers use the changelog expecting the comparison link shown in the PR description, the new heading has no corresponding comparison-link definition in `CHANGELOG.md`, so Markdown renders `[6.7.51]` as unlinked text and readers cannot open the release comparison.

Add the 6.7.51 comparison-link reference to `CHANGELOG.md`.

@18202781743 18202781743 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Release version and generated changelog metadata look correct.

@deepin-ci-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: 18202781743, deepin-bot[bot]

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

The pull request process is described 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
Contributor

TAG Bot

TAG: 6.7.51
EXISTED: no
DISTRIBUTION: unstable

@18202781743

Copy link
Copy Markdown
Contributor

/forcemerge

@deepin-bot

deepin-bot Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

This pr force merged! (status: blocked)

@deepin-bot
deepin-bot Bot merged commit 83397b0 into master Oct 15, 2026
32 of 36 checks passed
@deepin-bot

deepin-bot Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

TAG Bot

✅ Tag created successfully

📋 Tag Details
  • Tag Name: 6.7.51
  • Tag SHA: 967a7856209aa5b511e02bca7241569d7fe80a6c
  • Commit SHA: 83397b00b01b15ff7d8432a8a28cfca443c1fde6
  • Tag Message:
    Release dtkcore 6.7.51
    
    
  • Tagger:
    • Name: deepin-bot[bot]
  • Distribution: unstable

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants