Bump github.com/prometheus/common from 0.49.0 to 0.50.0

[dependabot]

Bumps github.com/prometheus/common from 0.49.0 to 0.50.0.

Release notes

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

v0.50.0

What's Changed

• Synchronize common files from prometheus/prometheus by @​prombot in prometheus/common#594
• Bump github.com/stretchr/testify from 1.8.4 to 1.9.0 in /sigv4 by @​dependabot in prometheus/common#593
• Bump github.com/aws/aws-sdk-go from 1.50.27 to 1.50.29 in /sigv4 by @​dependabot in prometheus/common#592
• Bump github.com/aws/aws-sdk-go from 1.50.29 to 1.50.31 in /sigv4 by @​dependabot in prometheus/common#595
• Remove unused 'Host' member from HTTPClientConfig by @​bboreham in prometheus/common#597
• Add OpenMetrics unit support by @​vesari in prometheus/common#544
• Remove deprecated version function by @​SuperQ in prometheus/common#591
• Synchronize common files from prometheus/prometheus by @​prombot in prometheus/common#599
• Bump golang.org/x/oauth2 from 0.17.0 to 0.18.0 by @​dependabot in prometheus/common#600
• Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 by @​dependabot in prometheus/common#601

Full Changelog: prometheus/common@v0.49.0...v0.50.0

Commits

• 944239f Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 (#601)
• 5f10b85 Bump golang.org/x/oauth2 from 0.17.0 to 0.18.0 (#600)
• a14ff55 Update common Prometheus files (#599)
• 6aadcf4 Remove deprecated version function (#591)
• 1e6ac24 Add unit (#544)
• 4199f18 Remove unused 'Host' member from HTTPClientConfig (#597)
• fa71e6a Bump github.com/aws/aws-sdk-go from 1.50.29 to 1.50.31 in /sigv4 (#595)
• 8a9fd7a Bump github.com/aws/aws-sdk-go from 1.50.27 to 1.50.29 in /sigv4 (#592)
• 8344367 Bump github.com/stretchr/testify from 1.8.4 to 1.9.0 in /sigv4 (#593)
• 0117d2f Update common Prometheus files (#594)
• 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]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[k8s-ci-robot]

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

I'm waiting for a kubernetes 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/test-infra repository.

[netlify]

✅ Deploy Preview for kubernetes-ingress-nginx canceled.

Name	Link
🔨 Latest commit	6acb9a0
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/65e99a186a3e0300089ae576

[cpanato]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, 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 [cpanato]

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

[Gacko]

/cherry-pick release-1.10

[k8s-infra-cherrypick-robot]

@Gacko: #11075 failed to apply on top of branch "release-1.10":

Applying: Bump github.com/prometheus/common from 0.49.0 to 0.50.0
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
Falling back to patching base and 3-way merge...
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump github.com/prometheus/common from 0.49.0 to 0.50.0
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.10

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/test-infra repository.