mirror of
https://github.com/pyenv/pyenv.git
synced 2025-11-08 11:33:49 -05:00
d64d1aa1e0
Some checks failed
macos_build / macos_build (3.10) (push) Has been cancelled
macos_build / macos_build (3.11) (push) Has been cancelled
macos_build / macos_build (3.12) (push) Has been cancelled
macos_build / macos_build (3.8) (push) Has been cancelled
macos_build / macos_build (3.9) (push) Has been cancelled
pyenv_tests / pyenv_tests (macos-13) (push) Has been cancelled
pyenv_tests / pyenv_tests (macos-14) (push) Has been cancelled
pyenv_tests / pyenv_tests (ubuntu-20.04) (push) Has been cancelled
pyenv_tests / pyenv_tests (ubuntu-22.04) (push) Has been cancelled
ubuntu_build / ubuntu_build (3.10) (push) Has been cancelled
ubuntu_build / ubuntu_build (3.11) (push) Has been cancelled
ubuntu_build / ubuntu_build (3.12) (push) Has been cancelled
ubuntu_build / ubuntu_build (3.8) (push) Has been cancelled
ubuntu_build / ubuntu_build (3.9) (push) Has been cancelled
1.1 KiB
1.1 KiB
Creating a release
The release of the new version of Pyenv is done via GitHub Releases.
Release checklist:
- Start drafting a new release on GitHub to generate a summary of changes.
Type the would-be tag name in the "Choose a tag" field and press "Generate release notes"- The summary may need editing. E.g. rephrase entries, delete/merge entries that are too minor or irrelevant to the users (e.g. typo fixes, CI)
- Update
CHANGELOG.mdwith the new version number and the edited summary (only the changes section) - Push the version number in
libexec/pyenv---version- Minor version is pushed if there are significant functional changes (not e.g. bugfixes/formula adaptations/supporting niche use cases).
- Major version is pushed if there are breaking changes
- Commit the changes locally into
master - Create a new tag locally with the same name as specified in the new release window
- Push the changes including the tag
- In the still open new release window, press "Publish release". The now-existing tag will be used.