chore: Trigger release.yml on published#222
Merged
Merged
Conversation
mattkram
reviewed
Jan 28, 2026
| # Only publish to PyPI if a tagged release | ||
| if: startsWith(github.event.ref, 'refs/tags/v') | ||
| # Only publish to PyPI for regular releases (not pre-releases, not main pushes) | ||
| if: github.event_name == 'release' && github.event.release.prerelease == false |
Collaborator
There was a problem hiding this comment.
Is false supposed to be a string? I feel like I've had "bool-as-string" in github actions in the past ...
Collaborator
Author
There was a problem hiding this comment.
I am giving this config a live run in another repo and I will specifically test this
mattkram
approved these changes
Jan 28, 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
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.
currently the release.yml workflow was triggered on push to main. Due to branch restrictions this can only happen on PR merge and Release through the UI.
What this PR does is respect the fact that we use the
publishedevent to push the tag to the repo. And by looking forgithub.event.release.prereleasewe can selectively apply the--label=devfor upload to anaconda.org and avoid publishing pre-releases to pypi.So in effect we would then be able to create pre-release from the main branch using the github UI after all appropriate PRs have been merged.