Repository navigation
Publish releases from version tags - #91
Merged
Merged
Conversation
- Release workflow on v* tags: checks the tag against main, __version__ and the changelog, runs the tests, builds, publishes to PyPI with trusted publishing after approval, creates the GitHub release and deploys docs - Release candidates go to TestPyPI - invoke release bumps the version and changelog; RELEASING.md describes the cycle - CI runs flake8 and mypy; docs list every module - Ship py.typed; ber-tlv accepts patch releases
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.
v*tags: the tag must be onmain, match__version__and have aCHANGELOG.mdsection; then tests,flit build+twine check, PyPI upload through trusted publishing in thepypienvironment, a GitHub release with the changelog section as notes and the built files attached, and the docs deployv0.5.0rc1) publish to TestPyPI onlypublish.ymlis removed: the GitHub release created by the new workflow would trigger it and upload twicetools/release.py(bump,check,notes) backsinvoke release <version>and the workflow;RELEASING.mddescribes the cycle and one-time setupkeycard tests tools example) and mypy;build.ymlkeeps only coverage;invoke docsregenerates the module pages, which now list every modulepy.typed;ber-tlv~=0.0.6Before tagging
v0.4.0, PyPI needs a trusted publisher (ownermmlado, repositorykeycard-py, workflowrelease.yml, environmentpypi), and GitHub needs apypienvironment with a required reviewer.