How to make a new release#
ArviZ uses the following process to cut a new release of the library.
Bump the version number in
- __version = "0.12.0" + __version = "0.12.1"
Update the release notes in
CHANGELOG.md. Remove any subsections within the released version without any items within them.
- ## v0.x.x Unreleased + ## v0.12.1 (2022 May 12)
Empty subheadings for the “unreleased” development version don’t need to be included yet.
Check versions in
setup.pyfiles. Arviz aims to follow the recommendations in SPEC-0 from scientific python.
Open a Pull Request including these changes. Make sure all CI tests pass, adding commits if necessary. Even if CI is passing on main, there might be new releases of dependencies that break CI.
Add a release in the Github release page once the PR is merged.
After the release on Github, the CI system will complete the rest of the steps. Including making any wheels and uploading the new version to PyPI.
Add a follow-up PR changing the version string to include the dev flag. Make sure the version string is PEP 440 compliant. For example, after releasing
v0.12.1it should be set to
Use the following template to add empty subheadings to the
CHANGELOG.mdfile in the follow-up PR.
## v0.x.x Unreleased ### New features ### Maintenance and fixes ### Deprecation ### Documentation
If the versions were updated in step 3, update also the conda forge recipe.