Address security vulnerabilities#102
Conversation
514d36f to
2baf5a0
Compare
|
Thanks for the PR @n0033! It's been a few years since the last commit to this project. Looks like a few of the CI pipelines have new failures unrelated to your changes, which LGTM. I'll look at getting CI patched up in the next day or so, then we can look at getting this PR merged! |
|
Hey @n0033 , things should be in a good place to re-attempt CI for this PR now! This failure should now be fixed on main https://github.com/zapier/prom-aggregation-gateway/actions/runs/22165817100/job/64092752198?pr=102 For the Keen to get this merged in and released! |
Signed-off-by: Norbert Wyszkowski <nwyszkowski@splunk.com>
ec83579 to
f8ea2e9
Compare
Signed-off-by: Norbert Wyszkowski <nwyszkowski@splunk.com>
Signed-off-by: Norbert Wyszkowski <nwyszkowski@splunk.com>
f8ea2e9 to
05ebf6d
Compare
I have updated the go version in |
|
Awesome, LGTM! Thanks for your patience |
In go version that is currently used (
1.21.3) there are some security vulnerabilities innet/httppackage:Also
golang.org/x/cryptohas following vulnerability:This MR:
1.21.3to1.25.6golang.org/x/cryptofromv0.12.0tov0.47.0Some validations:
go test
go run
metric push