Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Bump version to 6.1.13 #712

Merged
merged 1 commit into from
Dec 13, 2024
Merged

chore: Bump version to 6.1.13 #712

merged 1 commit into from
Dec 13, 2024

Conversation

fly602
Copy link
Contributor

@fly602 fly602 commented Dec 13, 2024

Bump version to 6.1.13

Bump version to 6.1.13
@deepin-ci-robot
Copy link

deepin pr auto review

代码审查意见如下:

  1. 版本号更新

    • 在提交的changelog中,版本号从6.1.12更新到6.1.13,这是一个合理的版本号更新。但是,在提交的changelog中,6.1.12版本被标记为unstable,而6.1.13版本也被标记为unstable。通常,版本号更新后,新版本应该标记为UNRELEASED,直到发布。建议检查版本号更新逻辑。
  2. 提交信息格式

    • 提交信息中,fixfeat关键字后面应该使用冒号和空格分隔,例如fix: 解决dconfig属性类型不对导致崩溃的问题。建议统一提交信息的格式,以提高可读性。
  3. 翻译更新

    • 提交信息中提到chore: update translations,但是没有具体说明更新了哪些翻译文件或内容。建议在提交信息中详细说明翻译更新的内容,以便其他开发者了解更新范围。
  4. 提交时间格式

    • 提交时间格式为Fri, 13 Dec 2024 14:47:41 +0800,这是一个标准的RFC 2822格式。但是,建议使用更易读的日期格式,例如2024-12-13 14:47:41 +0800
  5. 版本号重复

    • 在提交的changelog中,6.1.12版本被标记了两次,一次在更新后的版本信息中,一次在更新前的版本信息中。建议删除重复的版本号信息。

综上所述,建议对changelog文件进行以下修改:

  • 更新版本号更新逻辑,确保新版本标记为UNRELEASED
  • 统一提交信息的格式,使用冒号和空格分隔关键字和描述。
  • 在提交信息中详细说明翻译更新的内容。
  • 使用更易读的日期格式。
  • 删除重复的版本号信息。

Copy link

TAG Bot

TAG: 6.1.13
EXISTED: no
DISTRIBUTION: unstable

@deepin-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ECQZXC, fly602

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

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

@fly602 fly602 merged commit a770ecd into linuxdeepin:master Dec 13, 2024
17 checks passed
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