ci: publish to PyPI, and run lint and tests as one job - #2
Merged
Merged
Conversation
A published GitHub release builds the tag and uploads it to PyPI and the release page. Each merge to main uploads a dev pre-release, so the latest main installs with pip install --pre. Both use Trusted Publishing, and the version now comes from git tags via hatch-vcs.
zanjonke
approved these changes
Sep 28, 2026
zanjonke
left a comment
There was a problem hiding this comment.
🚀 LGTM!
The release process is the same as with codeplain. A small note: the tags need to be prefixed with a v eg. v0.1.1
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.
main:0.1.1.dev7is built and uploaded to PyPI.pip install --pre plain-parserinstalls itmainand manual runs:Versions come from git tags via hatch-vcs. Publishing uses PyPI Trusted Publishing, so no API token is stored.