-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sdist
not being uploaded along with the wheels.
#167
Comments
Tagging @ConorMacBride and @Cadair for assistance. |
I've been investigating this but I also don't understand what is going on. Will keep trying, but in the meantime I think it should be safe to upload a locally built sdist. |
The stcal package experienced the same issue (source distribution did not get uploaded to PyPi) today when it made a release. See the log: https://github.com/spacetelescope/stcal/actions/runs/6881432549/job/18717759512 |
Ok I'll try and investigate some more |
Mystery solved: #169 |
@WilliamJamieson - I've tagged a new release of the workflows so things should work properly next time. Let me know if not! |
I can confirm that this indeed fixed the issue. |
This is related to astropy/astropy#15597.
Background
The astropy 6.0rc1 release was triggered, which triggered the building and uploading of the astropy 6.0rc1 wheels to PyPi, see https://github.com/astropy/astropy/actions/runs/6817064464/job/18540287448. The issue is that the source distribution was not uploaded to PyPi along side all the pre-built wheels.
It looks like the
Run actions/upload-artifact@v3
step was successfully triggered by all of the wheel builds, see for example https://github.com/astropy/astropy/actions/runs/6817064464/job/18539760549. However, for the source distributionRun actions/upload-artifact@v3
was not triggered, see https://github.com/astropy/astropy/actions/runs/6817064464/job/18539753723.As far as I can tell, the source distribution upload would only be blocked by:
github-actions-workflows/.github/workflows/publish.yml
Lines 235 to 236 in 59a929b
This appears to be identical to the wheel upload blocker:
github-actions-workflows/.github/workflows/publish.yml
Lines 193 to 194 in 59a929b
Yet the former was blocked while the latter was not. Diving into the logs we see that for both the source and wheel builds the inputs both clearly have
upload_to_pypi: true
meaning that in both cases the upload should have occurred, seeSo I do not understand why one uploads while the other does not. There are no failures in any of the steps proceeding the failure.
The text was updated successfully, but these errors were encountered: