Something I tend to do now with my own libaries is make a copy of the produced wheels onto the initial release page. This way if pypi for whatever reason fails, users have another workaround on hand to use. If you need an example of what I am referring to I have a couple of cases on hand one of them being cyares https://github.com/Vizonex/cyares/releases/tag/v0.8.0.
A code snippet from that workflow does the trick (At least for my end)
#NOTE: Permissions need to have contents set to write.
permissions:
contents: write
upload_github:
needs: [build_wheels, build_sdist]
if: github.event_name == 'release' && github.ref_type == 'tag'
runs-on: ubuntu-latest
steps:
- uses: actions/download-artifact@v8
with:
path: dist
merge-multiple: true
# This will simply modify the given github release
# allowing for wheels to be uploaded to github's release
# page automatically.
- name: Upload Wheels To GitHub Release Page
uses: softprops/action-gh-release@v3
with:
token: ${{ secrets.GITHUB_TOKEN }}
files: dist/*
Something I tend to do now with my own libaries is make a copy of the produced wheels onto the initial release page. This way if pypi for whatever reason fails, users have another workaround on hand to use. If you need an example of what I am referring to I have a couple of cases on hand one of them being cyares https://github.com/Vizonex/cyares/releases/tag/v0.8.0.
A code snippet from that workflow does the trick (At least for my end)