Bump github.com/prometheus/client_golang from 1.20.0 to 1.20.2

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps github.com/prometheus/client_golang from 1.20.0 to 1.20.2.

Release notes

Sourced from github.com/prometheus/client_golang's releases.

v1.20.2

• [BUGFIX] promhttp: Unset Content-Encoding header when data is uncompressed. #1596

v1.20.1

This release contains the critical fix for the issue. Thanks to @​geberl, @​CubicrootXYZ, @​zetaab and @​timofurrer for helping us with the investigation!

• [BUGFIX] process-collector: Fixed unregistered descriptor error when using process collector with PedanticRegistry on Linux machines. #1587

Changelog

Sourced from github.com/prometheus/client_golang's changelog.

1.20.2 / 2024-08-23

• [BUGFIX] promhttp: Unset Content-Encoding header when data is uncompressed. #1596

1.20.1 / 2024-08-20

• [BUGFIX] process-collector: Fixed unregistered descriptor error when using process collector with PedanticRegistry on linux machines. #1587

Commits

• 67121dc Merge pull request #1596 from mrueg/fix-uncompressed-content-header
• 187acd4 Cut 1.20.2
• f7f8f3a fix: Unset Content-Encoding header when uncompressed
• 2254d6c Merge pull request #1587 from prometheus/fix-processcollector
• 4a15d05 Cut 1.20.1
• f2dd7b3 Use pedantic registry in other places too, to double check.
• 261fe84 bugfix: Pass network metrics to processCollector's Describe() function
• 5bf3341 Use NewPedanticRegistry in Process' Collector tests
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[k8s-ci-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions 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.

[netlify]

✅ Deploy Preview for kubernetes-sigs-jobset canceled.

Name	Link
🔨 Latest commit	157a1f1
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-jobset/deploys/66cc0043e9694a00086597c4

[kannon92]

/lgtm
/retest

[danielvegamyhre]

/retest

[danielvegamyhre]

Hmm what's going on with 1.27 e2e CI tests?

[kannon92]

I removed it from test-infra. Is there a GitHub ui required box that is checked?

Was there somewhere else I missed? Or is there a GitHub UI that we also used to mark it as required.

I did the same thing in Kueue and doesn’t look like there was any issue.

[ahg-g]

/retest

[ahg-g]

/lgtm cancel
/approve cancel

[ahg-g]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, dependabot[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ahg-g]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ahg-g]

/retest all

[k8s-ci-robot]

@ahg-g: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test pull-jobset-test-e2e-main-1-28
• /test pull-jobset-test-e2e-main-1-29
• /test pull-jobset-test-e2e-main-1-30
• /test pull-jobset-test-e2e-main-1-31
• /test pull-jobset-test-integration-main
• /test pull-jobset-test-unit-main
• /test pull-jobset-verify-main

Use /test all to run all jobs.

In response to this:

/retest all

Instructions 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.

[ahg-g]

/test all