-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Make this action play nicely with new gh upload/download artifact actions v4 #199
Comments
One option would be to support a recursive scan of |
FWIW, this restriction is inherited from |
If using |
This is already solved in the download action. Not sure if I want extra pattern matching here. |
Correct. Just to clarify, download-artifact just released v4.1 which includes a - uses: actions/download-artifact@v4
with:
path: dist
merge-multiple: true This is now just a documentation issue, to update the examples so folks know about this non-default switch. |
So this action doesn't showcase the use of matrices and other complex stuff. Neither does my PyPUG guide. |
Makes sense. I already have a PR for cibuildwheel docs: pypa/cibuildwheel#1705 |
GitHub recently updated the upload-artifact and download-artifact actions to v4. Dependabot is rolling them out.
A major breaking change relevant here is that v4 of upload-artifact no longer allows appending to the artifact. The recommended pattern depends on the old behavior, which now breaks if more than one runner creates artifacts, like when using cibuildwheel to build wheels for multiple platforms.
With v4 actions:
pypi-publish
step is trickier. The v4 action can download all artifacts, but it will unzip all the files into their own directories. One workaround is to manually flatten this back to adist/
thatpypi-publish
expects:This seems hacky. Could this action be improved to play better with the new versions of
actions/upload-artifact
andactions/download-artifact
?The text was updated successfully, but these errors were encountered: