terrateamio/terrateam#1397 ADD promote-v1 workflow to auto-move v1 tag on push to main - #620
Open
joshpollara wants to merge 1 commit into
Open
terrateamio/terrateam#1397 ADD promote-v1 workflow to auto-move v1 tag on push to main#620joshpollara wants to merge 1 commit into
joshpollara wants to merge 1 commit into
Conversation
…g on push to main Replace the manual "PR main -> v1" release step with a workflow that moves the v1 tag to main on every push and builds/pushes the action:v1 image. Delete ci.yaml, now superseded.
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.
Automates v1 releases so we no longer need a manual "PR main -> v1" step.
promote-v1.yaml: on every push to main, moves thev1tag to main and builds/pushesghcr.io/terrateamio/action:v1.ci.yaml(superseded; it built the image on push to thev1branch).v1becomes a moving tag instead of a branch. Tags aren't subject to branch protection, so the defaultGITHUB_TOKENcan move it — no PAT needed.Order of operations (post-merge cutover)
Run these once, after this PR merges to
mainand thepromote-v1workflow has run (that first run creates thev1tag).Safety check: in step 1, if the SHAs don't match, the workflow didn't run or the tag push failed — stop and check the Actions tab. Deleting the branch while the tag is missing would break
@v1for everyone.After cutover, every merge to
mainmovesv1forward automatically.Closes stategraph/stategraph#1397