In your example command, why is anaconda the index-url and PyPI extra-index-url? Does the order matter?

Please explain this setup in the dev docs. E.g., https://scipp.github.io/development/releasing-scipp.html

The order does matter, with pip index-url is the main index and extra-index-url is the fallback one. But if we start using uv it actually switches this order and breaks away from pip compatibilty astral-sh/uv#2083, so with uv this should be:

python -m uv pip install \
  --pre \
  --extra-index-url https://pypi.anaconda.org/scipp/simple \
  scipp

The triggered did upload all the wheels to https://pypi.anaconda.org/scipp/simple/scipp !
But it is also uploading these random doc links !? I'm not sure where it's getting these things.

The links all point to the latest docs. I don't think they are a big issue if they simply get overwritten.

Does the action overwrite existing wheels?

Does the action overwrite existing wheels?

No, it will only overwrite if they had the same name but they won't as it uses the commit hash in the name. We would need to setup a cleaning action to make sure we don't keep the old wheels around. https://github.com/scientific-python/upload-nightly-action/blob/main/.github/workflows/remove-wheels.yml as an example.

This looks pretty complicated. Do we really need all of this? Or is there a simple way to wipe the index every night before upload?

I'm waiting for a new release upstream https://github.com/scientific-python/upload-nightly-action first before merging this.