This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Update module github.com/prometheus/client_golang to v1.12.2 #3620
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.
Suggested by Renovate and Snyk, there is a medium sev reported in
prometheus/client_golang
which we could upgrade:This is just the one issue I noticed that we can do something about right away, I just decided to drop in and scope out potential changes for a next release since we are coming up on 30 days since the last one.
There are also critical reports from
pcre2/pcre2
introduced by our base image (alpine:3.15.4
), it's not clear when a new base image patch version will be released, so if we can mitigate this manually or just check for it in the resulting build, which I'm testing out now as I submit this.Perhaps it will be updated out without a rev in the base image, but I think we don't run
apk update
in our build process if it's not, so we may have to either change that, or wait for a new revision, and I'm inclined to just wait.Not exactly sure how they do things at Alpine HQ to be honest, but I'm sure they're on top of this, so maybe we want to delay a release until this all can be resolved out too, (I will look for it in the test build result):
The last recorded issue from the scan, which I'll mention just for completeness, is another one which I'm not sure we can do anything about, since SOPS @
v4
must likely contain a breaking change else it would not have got a major increment, I don't know if we can adopt this upgrade or if we've already covered this in prior discussions.(But I know the
jwt-go
vulnerability was mitigated in one of our most recent releases, thanks @pjbgf):I am not in any hurry to push the release button again, just testing. 👍