-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 #13489
Conversation
63d431b
to
e9e44b4
Compare
uses: actions/upload-artifact@v3 | ||
if: always() | ||
uses: actions/upload-artifact@v4 | ||
if: failure() |
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.
I adjusted this to only store these on failure, I think this is good enough? Then we do not have to store all the traces all the time when we do not need them.
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.
Traces should in general only be generated on failure - making this kinda moot - but we will save the ci time for the job running I guess.
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.
Jup, it seems to work, see here: https://github.com/getsentry/sentry-javascript/actions/runs/10593166442/attempts/1 there are two artifacts, for the two failed jobs.
It keeps complaining that this is deprecated, so bumping this to v4.