Repository navigation
ci(release): mint v*-rigel.N tags from rigel-release (RIG-5346) - #4
Merged
mattwilkinsonn merged 4 commits intoOct 15, 2026
Merged
Conversation
Add .github/rigel-version (1.1.0-rigel.1), the release-tag workflow and its script, and run the script test under the required CI check. Co-authored-by: Matt Wilkinson <matt@rigel.build>
…RIG-5346) Co-authored-by: Matt Wilkinson <matt@rigel.build>
Co-authored-by: Matt Wilkinson <matt@rigel.build>
Co-authored-by: Matt Wilkinson <matt@rigel.build>
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
2 participants
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
Adds release-tag minting on
rigel-release. It follows the autoscaler fork pattern fromrelease-tagging.md..github/rigel-versionis the single version source. The first value is1.1.0-rigel.1: upstream's latest tag is v1.1.0, and the fork has no tags.release-tag.yaml:checkvalidates a changed version, so N must be the next suffix.rigel-release,mintuses the automation App token (contents: write, this repo only) to createv<version>at the first-parent commit that set the version.CIjob.Verification
release-tag.test.shpasses all 8 cases: check-pr accept/skip/unchanged, the mint target, the existing tag, and same-target/conflicting 422.shellcheckis clean.actionlintis clean onrelease-tag.yaml. The only findings are on the oldsetup-go@v2andcheckout@v2pins ingolang.yml, which this PR leaves alone.Risks
forkReleaseMinter("nix2container")PR applies. Before that, the mint job has no App key and fails.v1.1.0-rigel.1at this commit.Refs: RIG-5346
Co-Authored-By: Matt Wilkinson matt@rigel.build