feat(release): adopt ecosystem release ceremony tooling#11
Merged
Conversation
Add release-check and release-cut tooling for base's container-only release surface, with workflow gates, operator documentation, changelog coverage, and shell regression/adoption tests. Refs #10
RUNA_REF validation now shares the same tag-or-SHA checkout substrate used by the Dockerfile, so metadata acceptance cannot outrun image build capability. release-cut now publishes main and the release tag with an atomic push and restores local release state if publication fails, keeping reruns clean. Refs #10
Release publication now uses a broad v-prefixed tag trigger and validates the exact release shape with release-check before container setup, so GitHub Actions minimatch semantics cannot block documented release tags. Refs #10
Release tag validators now reject leading-zero numeric identifiers across release-check, changelog headings, RUNA_REF tags, and the release workflow prerelease classifier. Refs #10 Refs tesserine/commons#26
Reject non-commit RUNA_REF SHA objects before checkout so the labeled ref matches the built commit. Document and test manual RC GitHub Release recovery with --prerelease so manual recovery matches the automated workflow classification. Refs #10
Fetch SemVer-shaped RUNA_REF values through refs/tags/<ref> so homonymous branches cannot shadow immutable release inputs. Cover both branch-shadowed tags and branch-only SemVer names with real-git regression coverage. Refs #10
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.
Summary
RUNA_REFvalidation match Dockerfile checkout capability and making release publication atomic/rerunnable.Changes
scripts/release-checkwithmetadata,notes, andreleasemodes for changelog, Dockerfile label surface, workflow, release notes, and optional container image identity checks.scripts/release-cutas the non-cargo release operation for stable and RC tags, with atomic remote publication ofmainplus tag.scripts/checkout-runa-refas the shared tag-or-SHA checkout substrate used by both metadata validation and the Dockerfile build.RELEASING.md, README release guidance, changelog entries, and split GitHub Actions workflows.GitHub Issue(s)
Closes #10
Test plan
./scripts/test-release-checkshellcheck scripts/checkout-runa-ref scripts/release-check scripts/release-cut scripts/test-release-check scripts/verify-release-adoption.sh./scripts/verify-release-adoption.sh./scripts/release-check metadatagit diff --checkpodman build --target runa-builder --build-arg RUNA_REF=969fe02d0a7e84b36cde67cfbc46e7550b08f22f .