[x] Manually trigger upstream CI tests for the release branch and ensure they are passed
[x] Update pinned dependencies versions in ./ci/requirements/py*-*-pinned.yml environment files using upstream CI tests information
[ ] Possibly update ./requirements.txt and ./docs/requirements.txt if the oldest dependencies versions were upgraded in the previous step
[x] Make sure that all CI tests are passed
[x] Activate and make sure the documentation for the release branch is built on RTD
Preparation conclusion
[x] Merge this PR to master
[x] Update release date in ./docs/whats-new.rst
[ ] Make sure all CI tests are passed and RTD doc is built on the master branch
Publish the release
[x] "Draft a new release" on GitHub.
Choose a release tag v0.1.14, fill in the release title and click on the Auto-generate release notes button.
This will trigger the publish Github action that will push the release on Pypi.
[x] Last check the ./setup.py file version of the release and that the documentation is ready
[ ] Publish !
[ ] Checkout on Pypi and Conda that the new release is distributed.
Setup
git checkout -b releasev0.1.14./docs/whats-new.rst./setup.pyPrepare code for release
Code clean-up
codespell -q 2Software distribution readiness
./ci/requirements/py*-*-pinned.ymlenvironment files using upstream CI tests information./requirements.txtand./docs/requirements.txtif the oldest dependencies versions were upgraded in the previous stepPreparation conclusion
./docs/whats-new.rstPublish the release
Auto-generate release notesbutton.This will trigger the publish Github action that will push the release on Pypi.
./setup.pyfile version of the release and that the documentation is readyCI tests / RTD build results