Skip to content

ci: publish to PyPI, and run lint and tests as one job - #2

Merged
bananaplain merged 2 commits into
mainfrom
ci/publish-to-pypi
Sep 29, 2026
Merged

bananaplain merged 2 commits into
mainfrom
ci/publish-to-pypi

Conversation

@bananaplain

Copy link
Copy Markdown
Collaborator
  • On a published GitHub Release:
    • the tagged version is built, uploaded to PyPI, and its files are attached to the release.
  • On each merge to main:
    • a dev pre-release such as 0.1.1.dev7 is built and uploaded to PyPI.
    • pip install --pre plain-parser installs it
  • On pull requests, pushes to main and manual runs:
    • lint and tests run as one job.

Versions come from git tags via hatch-vcs. Publishing uses PyPI Trusted Publishing, so no API token is stored.

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 zanjonke left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 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

@bananaplain
bananaplain merged commit cfc9d0b into main Sep 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants