chore(ci): reduce Node.js 20 deprecation warnings in workflows#7722
chore(ci): reduce Node.js 20 deprecation warnings in workflows#7722SipengShen01 wants to merge 1 commit into
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release-1.17 #7722 +/- ##
================================================
+ Coverage 42.01% 42.02% +0.01%
================================================
Files 874 874
Lines 53571 53571
================================================
+ Hits 22508 22515 +7
+ Misses 29376 29371 -5
+ Partials 1687 1685 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
a7ul/tar-action, softprops/action-gh-release,aquasecurity/trivy-action upgrade add dco Signed-off-by: shensipeng <sipeng@whu.edu.cn>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This PR reduces dependency on the deprecated Node.js 20 runtime in GitHub Actions workflows, as warned by GitHub. The following changes are made:
aquasecurity/trivy-actionfrom v0.35.0 (commit hash) to v0.36.0 (tag) to remove Node.js 20 usage.softprops/action-gh-releasefrom v2 to v3.0.1 for the same reason.a7ul/tar-action@v1.2.0with a directtarcommand (tar -czf crds.tar.gz -C ./charts/karmada crds). The action is no longer maintained and still relies on Node.js 20; the built-intarcommand is fully equivalent and removes the external dependency.The
slsa-framework/slsa-github-generatorremains at v2.1.0 because that is currently the latest version and still uses Node.js 20 internally.Which issue(s) this PR fixes:
Fixes #7702
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?: