Release 6.0.37

[deepin-bot]

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.0.37 - 2025-06-19

Changed

• From linuxdeepin/dtkdeclarative
• From linuxdeepin/dtkdeclarative
• From linuxdeepin/dtkdeclarative
• From linuxdeepin/dtkdeclarative
• Support VERSION file and auto release (feat: Support VERSION file and auto release #262)
• From linuxdeepin/dtkdeclarative
• From linuxdeepin/dtkdeclarative
• From linuxdeepin/dtkdeclarative

Summary by Sourcery

Prepare release 6.0.37 by updating version metadata and adding a standardized changelog

Enhancements:

• Bump Arch Linux PKGBUILD package version to 6.0.37
• Add CHANGELOG.md in Keep a Changelog format to document notable changes
• Introduce VERSION file support to enable automated releases (feat: Support VERSION file and auto release #262)

[sourcery-ai]

Reviewer's Guide

This PR prepares the 6.0.37 release by bumping the package version, introducing a VERSION file for automated releases, and adding a formal CHANGELOG.md with the new release notes.

Class diagram for release versioning and changelog files

classDiagram
    class PKGBUILD {
        - pkgver: string
        - pkgrel: int
        - sourcename: string
        - sourcetars: list
    }
    class VERSION {
        + version: string
    }
    class CHANGELOG_md {
        + changelog: string
    }
    PKGBUILD --> VERSION : references
    PKGBUILD --> CHANGELOG_md : references
    VERSION <.. CHANGELOG_md : documents

Loading

File-Level Changes

Change	Details	Files
Package version bumped for Release 6.0.37	Updated pkgver from 6.0.0 to 6.0.37	archlinux/PKGBUILD
Introduced changelog and release automation	Created CHANGELOG.md following Keep a Changelog format Added VERSION file to drive auto release workflow	CHANGELOG.md VERSION

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[deepin-ci-robot]

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.

[github-actions]

TAG Bot

TAG: 6.0.37
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

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