@@ -62,22 +62,20 @@ whatever you need with ``uv run``.
6262Creating a New Release
6363^^^^^^^^^^^^^^^^^^^^^^
6464
65- New releases are made using the following steps:
65+ These steps for creating a new release are proposed to be taken only after
66+ ensuring that CI (unit tests, sphinx for RTD _, build of wheel and source distribution)
67+ raised no errors.
6668
6769#. Bump version number in ``sfs/__init__.py ``
6870#. Update ``NEWS.rst ``
6971#. Commit those changes as "Release x.y.z"
7072#. Create an (annotated) tag with ``git tag -a x.y.z ``
71- #. Clear the ``dist/ `` directory
72- #. Create a source distribution with ``python3 setup.py sdist ``
73- #. Create a wheel distribution with ``python3 setup.py bdist_wheel ``
74- #. Check that both files have the correct content
75- #. Upload them to PyPI _ with twine _: ``python3 -m twine upload dist/* ``
76- #. Push the commit and the tag to Github and `add release notes `_ containing a
77- link to PyPI and the bullet points from ``NEWS.rst ``
78- #. Check that the new release was built correctly on RTD _
79- and select the new release as default version
80-
81- .. _twine : https://twine.readthedocs.io/
73+ #. Push the commit and the tag to Github
74+ #. The workflow ``.github/workflows/publish.yml `` will handle the build and the
75+ upload to PyPI
76+ #. `Add release notes `_ containing a link to PyPI and the bullet points
77+ from the updated ``NEWS.rst ``
78+ #. Select the new release as the default on RTD _
79+
8280.. _add release notes : https://github.com/sfstoolbox/sfs-python/tags
8381.. _RTD : https://readthedocs.org/projects/sfs-python/builds/
0 commit comments