Skip to content

Commit 6316f32

Browse files
authored
Update preparing_releases_and_hotfixes.rst (#413)
1 parent 5b3ae0e commit 6316f32

File tree

1 file changed

+0
-15
lines changed

1 file changed

+0
-15
lines changed

doc/source/preparing_releases_and_hotfixes.rst

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,6 @@ Summary of tasks
5757
* Check automated testing of source distribution and wheel generation and upload
5858
* Create a new release from newly created tag
5959
* Check that deployment actions have adequately pushed dist and wheels to PyPi
60-
* Manually upload Cirrus CI wheels (temporary)
6160
* Update `conda-forge` packages
6261
* Create a blog post outlining the release
6362
* Increment develop branch files ready for the next version
@@ -144,20 +143,6 @@ If everything works, you can now complete the release by:
144143
#. If the action fails and some files have been uploaded, then you will not be able to re-upload to PyPI. At this point you will need to yank the release from PyPI and create a new minor version and re-deploy it.
145144

146145

147-
Manually upload Cirrus CI wheels (temporary)
148-
--------------------------------------------
149-
150-
Unfortunately the deployment of Cirrus CI generated wheels (for `osx-arm64` and `linux-aarch64`) does not get properly triggered by a release. However, they are properly uploaded to `TestPyPi`_
151-
152-
#. Go to the recently updated TestPyPi release and download all the `.whl` files which have the tags `arm64` and `aarch64`.
153-
154-
#. From a local directory upload these wheels using ``twine``.
155-
156-
.. code-block:: bash
157-
158-
twine upload -r pypi *.whl --verbose
159-
160-
161146
Update `conda-forge` packages
162147
-----------------------------
163148

0 commit comments

Comments
 (0)