Backport of [NET-2420] security: Upgrade helm containerd and several other dependencies into release/1.1.x #3638
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #3625 to be assessed for backporting due to the inclusion of the label backport/1.1.x.
🚨
The person who merged in the original PR is:
@zalimeni
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
This upgrades several dependencies to address open CVEs in the
cli
module (caused by our consumption of 3rd-party libs for API clients that are bundled w/ unused runtimes, where a non-impacting vulnerability actually exists) and cross-compatibility between upgraded modules.This will allow us to re-enable release blocks on Go module scan results in CRT, previously disabled in:
Changes proposed in this PR
Upgrade the following (split by commit to aid review):
helm/v3
3.9.4 -> 3.11.3k8s.io/
dependencies 1.26.? -> 1.26.10 to matchcontroller-runtime
/helm
containerd
1.3.0 -> 1.7.13 (latest)docker/docker
23.0.3+incompatible -> 25.0.2+incompatible (latest)oras.land/oras-go
1.2.2 -> 1.2.5 to fix docker incompatibilitydocker/distribution
2.8.1+incompatible -> 2.8.3+incompatible (latest)cyphar/filepath-securejoin
0.2.3 -> 0.2.4 (latest 0.x patch)Automated backports will almost certainly fail, but I've added the labels JIC they're successful and to make it clear this should be backported.
How I've tested this PR
CI and acceptance tests continue to pass.
How I expect reviewers to test this PR
👀 + 💭
Checklist
Overview of commits