ci: fork-only releases via fork_revision (v1.13.3.1) - #11
Merged
Conversation
The pipeline derives the version strictly from the upstream tag contained in develop, so a release without an upstream bump was impossible: dispatching found "1.13.3, already published" and stopped. That was the deliberate design — but we now need exactly such a release. `fork_revision` (dispatch only, validated as a positive integer) appends a fourth component: 1 → v1.13.3.1. Upstream's number stays visible in front, the tag sorts after v1.13.3, and the automatic push path is untouched — it never sets the input, so a merge still only ever cuts the upstream version. CHANGELOG.md gains the v1.13.3.1 section the release gate requires; FORK_CHANGES.md records the versioning rule.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We need a new release without code changes. The pipeline could not do that: it derives the version strictly from the upstream tag contained in
develop, so a dispatch found "1.13.3, already published" and stopped — exactly as designed in #9, where a fourth version component was considered and rejected. This reverses that decision, narrowly.fork_revision— dispatch onlyRun Release manually with
fork_revision: 1and the version becomes<upstream>.<revision>→v1.13.3.1. Upstream's number stays visible in front and the tag sorts afterv1.13.3. The input is validated as a positive integer (0,01,abc,1.5are refused with a clear error).The automatic push path is untouched: it never sets the input, so a merge into
developstill only ever cuts the upstream version. Afterv1.13.3.1is published, a normal push resolves1.13.3, finds it published, and no-ops as before; the next upstream bump cutsv1.13.4normally.Everything downstream works unchanged with the longer version string — ldflags injection, the binary smoke test (
wings v1.13.3.1), the CHANGELOG gate (anchored, so## v1.13.3still does not match## v1.13.3.1and vice versa), image tags:1.13.3.1/:v1.13.3.1,:latestby digest.Also
CHANGELOG.md:## v1.13.3.1section — required by the gate, becomes the release notes.FORK_CHANGES.md: the versioning rule on the release-pipeline row.v1.13.3.1is built from the same sources asv1.13.3.Verification
actionlint(with shellcheck) clean.'',1,2,0,01,abc,1.5.v1.13.3andv1.13.3.1.After merge
Merging triggers the usual push run, which no-ops (
1.13.3is published). Then dispatch Release ondevelopwithfork_revision = 1to cutv1.13.3.1.