-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
ci: update actions/upload-artifact to v4 with merge #2158
Conversation
the new before:
after:
|
This reverts commit 6ff2435.
Hey @joshuarli, thanks for the PR. Just to confirm, have you tested already that this works, or is the only way to know for sure to attempt a new Sentry CLI release? |
I demonstrated above that the structure of the release artifact 8c24c96.zip is the same (cleaner). Build: https://github.com/getsentry/sentry-cli/actions/runs/10929197033 But yes, we won't know for sure until a new release is run in full since that has to go through craft. |
This reverts commit 5e71dcc.
Retrying upload-artifact v4 update (see #2119) by using artifacts/merge to merge together multiple artifacts from different jobs into the single one named github.sha that craft expects.
Summarily, upload-artifact v3 is deprecated but v4 doesn't support mutating an artifact with the name name by uploading different filepaths to the same artifact. Because we need a single artifact "github.sha", we have to use actions/merge to create it. Alternatively craft could be modified but this is the easiest way forward and I like the idea of a unified artifact, it makes craft simpler.
ref: getsentry/craft#552