Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 09:26:52 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clarify BCQuality minor is monotonic and never resets across major bumps

Browse source
This commit is contained in:
wenjiefan 2026-07-13 10:50:26 +02:00
parent 662b47c45d
commit 1dc6fa4b8d
1 changed files with 6 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

9
.github/workflows/release-version.yml vendored
View file

@ -5,9 +5,12 @@
# The release version is a `major.minor` value in the repo-root VERSION file. # The release version is a `major.minor` value in the repo-root VERSION file.
# This workflow tags the current commit as `v{VERSION}` and refuses to re-tag an # This workflow tags the current commit as `v{VERSION}` and refuses to re-tag an
# existing version, so bumping VERSION is the deliberate act that starts a new # existing version, so bumping VERSION is the deliberate act that starts a new
# release. Bump the minor for the usual ~monthly content release, the major for a # release. The minor is a monotonic counter: bump it (only ever increment, never
# breaking change. Downstream, the PR-review engine pins this version in its # reset) for the usual ~monthly content release; bump the major for a breaking
# bcquality.config.yaml and embeds its MINOR as the 3rd segment of its own tag. # change but keep incrementing the minor across it. Because the minor is never
# reused, it uniquely identifies a release. Downstream, the PR-review engine pins
# this version in its bcquality.config.yaml and embeds this MINOR as the 3rd
# segment of its own tag.
name: Release version name: Release version