ci: remove the auto-tag-on-merge release workflow#13
Merged
Conversation
release.yaml bumped and pushed a version tag on every push to main via anothrNick/github-tag-action, so routine merges (CI, docs) would mint releases. Tagging should be deliberate. Remove it; cut tags manually when actually releasing. (It had also been failing on recent merges, so no tags were created.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
release.yamlrananothrNick/github-tag-actionon every push to main, bumping and pushing a new version tag. That means routine merges (CI changes, docs) mint releases, which isn't what we want — tagging should be deliberate.Removing the workflow. Releases happen by tagging manually when we actually intend to release. (The workflow had also been failing on recent merges, so no tags were created by it.)
No other oasdiff repo auto-tags on merge (oasdiff uses goreleaser on tag push, which is deliberate).