-
Notifications
You must be signed in to change notification settings - Fork 49
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
Bump download/upload artifact gha version #396
Conversation
@@ -72,7 +72,7 @@ jobs: | |||
UDUNITS2_XML_PATH: ${{ matrix.xml_path }} | |||
CIBW_ENVIRONMENT_PASS_LINUX: UDUNITS2_INCDIR UDUNITS2_LIBDIR UDUNITS2_XML_PATH | |||
|
|||
- uses: actions/upload-artifact@v3 | |||
- uses: actions/upload-artifact@v4 | |||
with: | |||
name: pypi-artifacts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we've seen the basic v3-to-v4 changes is that artifacts are now immutable and non-rewritable
So I think the problem here is probably that the artifact name must be different for each usage,
so, something like pypi-artifacts-${{ matrix.os }}-${{ matrix.arch }}
might work ?
It seems like that, now we are storing different ones in different places, the other tasks will also probably need updating? TBH I'm a bit out of my depth with this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, there is now no artifact merging and names have to be unique
I think the best option here for I recommend that we sit tight and wait for the dust to settle, as community pressure may force a change or a documented best practice pattern may emerge for the common |
🚀 Pull Request
Description
Require to bump the version of the
download-artifact
andupload-artifact
to the latest version (@3
->@4
) consistently within the same pull-request.