-
Notifications
You must be signed in to change notification settings - Fork 56
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
Pin version for all actions via SHA rather than floating tag #1220
Conversation
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.
Minor comment but LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amisevsk, AObuchow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Pin all actions used in workflows to the current latest bugfix release within their major version (e.g. v3 -> [hash for] v3.6.1) * Update all instances of docker/build-push-action to use latest v4 release instead of a mix of v3 and v4 * Remove mattermost message steps from release job, as mattermost is gone now. Signed-off-by: Angel Misevski <[email protected]>
c88ff7c
to
843e514
Compare
New changes are detected. LGTM label has been removed. |
/retest |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1220 +/- ##
==========================================
- Coverage 52.74% 52.70% -0.04%
==========================================
Files 84 84
Lines 7616 7616
==========================================
- Hits 4017 4014 -3
- Misses 3310 3312 +2
- Partials 289 290 +1 ☔ View full report in Codecov by Sentry. |
What does this PR do?
docker/build-push-action
to use latest v4 release instead of a mix of v3 and v4Note: in most cases, there's a new major version for our actions (usually around switching from Node 16 -> 20. This PR does not switch major versions (except for some instances of
docker/build-push-action
) to avoid any risk of breaking anything -- ideally these are the exact same versions of each action we're using right now.What issues does this PR fix or reference?
N/A
Is it tested? How?
N/A
PR Checklist
/test v8-devworkspace-operator-e2e, v8-che-happy-path
to trigger)v8-devworkspace-operator-e2e
: DevWorkspace e2e testv8-che-happy-path
: Happy path for verification integration with Che