-
-
Notifications
You must be signed in to change notification settings - Fork 403
Update artifact-related actions #2679
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
Conversation
In this case we should be fine since there is just one job that uploads the artifacts.
In this case the uploaded artifacts uses different paths and names, there should be no breaking changes.
In this case the jobs exploited the previous action behaviour when uploading multiple artifacts under the same "name". To upgrade to v4 we need to upload artifacts with unique "name" and merge them when downloading using the "pattern" property.
This job got the same changes made in the publish-go-nightly job.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2679 +/- ##
=======================================
Coverage 70.22% 70.23%
=======================================
Files 222 222
Lines 21348 21348
=======================================
+ Hits 14992 14993 +1
+ Misses 5177 5176 -1
Partials 1179 1179
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
LGTM
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.
Thanks Cris 💯
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
Updates the artifacts-related actions to the latest version:
Here the migration guide > https://github.com/actions/download-artifact/blob/main/docs/MIGRATION.md
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
Other information
If the testing is successful, I will update the tooling asset repo too.