|
| 1 | +# Release instructions for jupyter-sphinx |
| 2 | + |
| 3 | +Jupyter Sphinx uses a GitHub action to automatically push a new release to |
| 4 | +PyPI when a GitHub release is added. |
| 5 | + |
| 6 | +To cut a new Jupyter Sphinx release, follow these steps: |
| 7 | + |
| 8 | +* Ensure that all tests are passing on master. |
| 9 | +* In [`_version.py`](https://github.com/jupyter/jupyter-sphinx/blob/master/jupyter_sphinx/_version.py), |
| 10 | + change the "release type" section to "final" e.g.: |
| 11 | + |
| 12 | + ```python |
| 13 | + version_info = (0, 2, 3, "final") |
| 14 | + ``` |
| 15 | +* Make a release commit and push to master |
| 16 | + |
| 17 | + ``` |
| 18 | + git add jupyter_sphinx/_version.py |
| 19 | + git commit -m "RLS: 0.2.3" |
| 20 | + git push upstream master |
| 21 | + ``` |
| 22 | +* [Create a new github release](https://github.com/jupyter/jupyter-sphinx/releases/new). |
| 23 | + The target should be **master**, the tag and the title should be the version number, |
| 24 | + e.g. `0.2.3`. |
| 25 | +* Creating the release in GitHub will push a tag commit to the repository, which will |
| 26 | + trigger [a GitHub action](https://github.com/jupyter/jupyter-sphinx/blob/master/.github/workflows/artifacts.yml) |
| 27 | + to build `jupyter-sphinx` and push the new version to PyPI. |
| 28 | + [Confirm that the version has been bumped](https://pypi.org/project/jupyter-sphinx/). |
| 29 | +* In [`_version.py`](https://github.com/jupyter/jupyter-sphinx/blob/master/jupyter_sphinx/_version.py), |
| 30 | + bump the minor version and change the "release type" section to "alpha" e.g.: |
| 31 | + |
| 32 | + ```python |
| 33 | + version_info = (0, 2, 4, "alpha") |
| 34 | + ``` |
| 35 | +* That's it! |
0 commit comments