chore: Release v2.19.0#2949
Conversation
|
This issue is currently awaiting triage. If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the The DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
|
||
| NOTE: This release addresses a security vulnerability (GHSA-g3c8-4qh2-rhrg) where `/debug/pprof/*` endpoints were not protected by the `--auth-filter` flag. The endpoints have been moved to the telemetry server and are now correctly gated. See [#2924](https://github.com/kubernetes/kube-state-metrics/pull/2924) for details. Credits to @vldevadath for responsible disclosure. | ||
|
|
||
| * This release builds with Go `v1.26.1` |
There was a problem hiding this comment.
Can we bump this to 1.26.2 before the release? Thanks
26ade53 to
9f939dd
Compare
Update data.yml and examples docs: regenerate README with v2.19.0 compatibility matrix entry
| * chore: Rebase [#2924](https://github.com/kubernetes/kube-state-metrics/pull/2924) with an additional commit by @rexagod in [#2947](https://github.com/kubernetes/kube-state-metrics/pull/2947) | ||
| * chore: bump Go from 1.26.1 to 1.26.2 by @bhope in [#2950](https://github.com/kubernetes/kube-state-metrics/pull/2950) | ||
|
|
||
| ## New Contributors |
There was a problem hiding this comment.
We usually don't have these in the changelog
There was a problem hiding this comment.
Ah, so that's only in the release notes. Thanks for pointing that out, I will take it out.
There was a problem hiding this comment.
Removed sections: Full changelog and new contributors.
|
/approve (for @mrueg to take a look post their review, and unhold) |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bhope, rexagod The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
It seems we've identified a severe bug downstream, which I'd ideally like to push here to save us the trouble of cutting a new patch release immediately after. Investigating, will update here. |
Release v2.19.0
Part of #2919