-
Notifications
You must be signed in to change notification settings - Fork 19
Making a release
Mathieu Scheltienne edited this page Jan 16, 2024
·
5 revisions
This is a very rough draft of how to make a release. Most likely generalization to any repo that follows the mne-icalabel structure with docs and versioning. The example below is for release 0.6.0.
- Update the version
- In
pyproject.toml - Rename
doc/changes/latest.rstto0.6.rst - In
doc/changes/index.rst, removelatest.rstin favor of0.6.rst - Merge the changes
- In
- Build the documentation localy
- Checkout the
gh-pagesbranch- Rename
stableto0.5 - Copy the build documentation to
stable(thedevfolder will be overwritten later) - Push the changes
- Rename
- Create a new release
- Tag and title name is
v0.6.0 - In the
Actions, make sure the publication workflow succeeded. If the workflow failed, fix the failure and trigger the workflow manually.
- Tag and title name is
- Checkout and push a new branch
maint/0.6from the most recent commit - Update the version to the next dev
- In
pyproject.toml - Remove sphinx tag
.. _latestin0.6.rst - Copy and edit
latest.rstfrom template - Add
latest.rsttodoc/changes/index.rst - Update versions in
doc/_static/versions.json
- In
-
conda-forgeshould automatically open a PR to update the feedstock