Bump the version in lambdex/version.py
and update
CHANGES.md
with any changes that are likely to be useful to consumers and then open
a PR with these changes and land it on https://github.com/pex-tool/lambdex main.
Sync a local branch with https://github.com/pex-tool/lambdex main and confirm it has the version bump and changelog update as the tip commit:
$ git log --stat -1 HEAD
commit 1ce9fa95893b05bc0bc3a9a7d9c415deeb14d447 (HEAD -> main, origin/main, origin/HEAD)
Author: John Sirois <[email protected]>
Date: Mon Apr 26 12:36:53 2021 -0800
Prepare the 0.1.4 release. (#21)
lambdex/version.py | 2 +-
CHANGES.md | 41 +++++++
2 files changed, 42 insertions(+), 1 deletions(-)
Tag the release as v<version>
and push the tag to https://github.com/pex-tool/lambdex main:
$ git tag --sign -am 'Release 0.1.4' v0.1.4
$ git push --tags https://github.com/pex-tool/lambdex HEAD:main
The release to PyPI is automated but requires approval from at least one Core or Maintainers team member. These folks will all get an email with a link to the GitHub release workflow to do this. Alternatively, they can open the Release workflow here and navigate to the release approval widget.