Release workflow#151
Merged
Merged
Conversation
Add comments reherse tag
Erotemic
force-pushed
the
release-workflow
branch
from
9948bdd to
b36ffe1
Compare
This was referenced Jun 1, 2026
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.
Removes the old publish.yml and adds release.yml which is tied to the trusted pypi environments.
This should allow for publishing a release when pushing to the "release" branch. It will create a new github tag based on that version as well as a github release.
There is a similar version that runs if you push to "test-release", but it doesn't actually publish the tag and it pushes to test.pypi.