Repository navigation
Publish a GitHub Release from main - #21
Merged
Merged
Conversation
The release tag comes from the version in setup.py. The same version refreshes that release's packages. A version bump publishes the next release. Co-authored-by: Fan Feilong <fanfeilong@gmail.com>
fanfeilong
marked this pull request as ready for review
October 14, 2026 09:54
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.
A push to
mainnow publishes a GitHub Release. The tag isvplus the version insetup.py, currentlyv0.12.0. The release carries the Python package and the skills zip.The same version updates that release's files. Changing the version in
setup.pypublishes the next release. Pull requests still only upload workflow artifacts.This still does not publish to PyPI.