fix: Fix CI/CD pipeline trying to double release on commits to main#532
Merged
charlesvien merged 2 commits intomainfrom Jan 17, 2026
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jan 17, 2026
k11kirky
approved these changes
Jan 17, 2026
Base automatically changed from
01-17-fix_typecheck_failing_on_torchglow
to
main
January 17, 2026 20:52
4d87684 to
feb4482
Compare
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.

Earlier in the week, I was trying to make it so if I push a major or minor bump through git tags that the CI/CD workflows will release the new version instead of having to wait for a new commit to main to release a new version. Now it's doing both, on commits to main and also on git tag (which commit to main create a tag per commit)
This PR fixes it by splitting the pipeline into two workflows the first one will create a tag on commits to main, then new tags create actual releases.