Repository navigation
Automate versioned releases behind a green-Self-test gate - #3
Merged
Merged
Conversation
Releases were cut by hand (tag, release notes, moving v1 tag). The new Release workflow (workflow_dispatch on main) refuses to release unless Self-test is green for the exact commit, derives the next version from conventional-commit subjects since the last tag when no explicit version is given (feat or breaking -> minor, fix -> patch; breaking bumps minor on the 0.x line), re-points the v1 moving tag, and publishes grouped notes. cut-release.sh has a --dry-run mode for local preview; the dry run against current main derives v0.2.0 (first use: publish PR #2).
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
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.
What
Automates cutting versioned releases of cce-action, so "tags are published after self-test CI is green" (README) becomes one click instead of a manual tag/release dance.
New
Releaseworkflow (workflow_dispatch on main)v0.2.0), or be left empty to derive the next version from commit subjects since the last tag (feat/feat!→ minor bump,fix→ patch bump; on the 0.x line a breaking change bumps minor, not major, matching this repo'sv0.xreleases under thev1moving tag).v1at the release (best-effort with a::warning::if a tag-protection rule blocks the force push — the release itself is still published).Scripts
.github/scripts/cut-release.sh— the whole flow, with a--dry-runmode for local preview: prints the target, derived version, range, and rendered notes without tagging anything. Rejects an already-existing tag..github/scripts/classify-commits.py— subject classification + version bump + notes rendering; classification reason printed to stderr.README
Versioning section now documents the Release workflow, the bump policy, and the local dry-run command.
Verification (local, against real repo state)
bash -n/py_compile/ YAML parse all clean.3ffab6e, sincev0.1.1): derives v0.2.0 (PR Add scan-timeout guard, debug log-flood warning, and JS self-test #2's "Add scan-timeout guard..." → minor), notes grouped Features/Fixes correctly.feat:→ v0.3.0,fix(mapper):→ v0.2.1,feat!:→ v0.3.0 (0.x breaking policy),chore:/docs:→ v0.2.1; same logic on av1.2.3base → 1.3.0 / 1.2.4 / 1.3.0.RELEASE_VERSIONoverride honored, existing tag rejected with an actionable error,NOTES_LINEappears at the top of the notes.git log ... || true | python3skipped the classifier entirely.First use
After this merges and Self-test is green, run the Release workflow on main with an empty version — it derives v0.2.0 and moves
v1, publishing thescan-timeoutinput, the debug log warning, and the JAVASCRIPT self-test from #2.Follow-ups (not in this PR)
workflow_runon Self-test success instead of a manual dispatch, if you want a release on every green merge.actions/checkout@v4/actions/upload-artifact@v4target Node 20 (deprecation warning in current runs); a bump to v5 clears the annotation.