Bump helm to version 3.14.2 to fix high vulnerability #6785
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.
Hi,
According to quay.io, there is a high vulnerability in helm versions < 3.14.2
https://quay.io/repository/operator-framework/helm-operator/manifest/sha256:fb11fef1bb0e44b55cc9a111521554be1af18feb15ed41f7695afb37b2b65aca?tab=vulnerabilities
This is causing a problem to release a new version of our operator in konflux because the vulnerability is deemed critical in our case and it doesn't allow us to release it.
The PR contains a change to
go.mod
to bump helm from 3.13.3 to 3.14.2 and the cascading changes due togo mod tidy
andgo mod vendor
with golang v1.21.12