Skip to content

[backport] build(deps): Bump github.com/prometheus/common from 0.67.4 to 0.67.5 (#1259)#1268

Open
mergify[bot] wants to merge 1 commit intorelease/v1.6from
mergify/bp/release/v1.6/pr-1259
Open

[backport] build(deps): Bump github.com/prometheus/common from 0.67.4 to 0.67.5 (#1259)#1268
mergify[bot] wants to merge 1 commit intorelease/v1.6from
mergify/bp/release/v1.6/pr-1259

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jan 18, 2026

Bumps github.com/prometheus/common from 0.67.4 to 0.67.5.

Release notes

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

v0.67.5

What's Changed

Full Changelog: prometheus/common@v0.67.4...v0.67.5

Commits
  • 934ff37 build(deps): bump google.golang.org/protobuf from 1.36.10 to 1.36.11 (#870)
  • 1e29804 build(deps): bump golang.org/x/net from 0.46.0 to 0.48.0 (#872)
  • 0bd1c40 Synchronize common files from prometheus/prometheus (#866)
  • b644201 build(deps): bump golang.org/x/oauth2 from 0.32.0 to 0.34.0 (#871)
  • See full diff in compare view

Dependabot compatibility score

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)

This is an automatic backport of pull request #1259 done by [Mergify](https://mergify.com).

…1259)

Bumps [github.com/prometheus/common](https://github.com/prometheus/common) from 0.67.4 to 0.67.5.
- [Release notes](https://github.com/prometheus/common/releases)
- [Changelog](https://github.com/prometheus/common/blob/main/CHANGELOG.md)
- [Commits](prometheus/common@v0.67.4...v0.67.5)

---
updated-dependencies:
- dependency-name: github.com/prometheus/common
  dependency-version: 0.67.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
(cherry picked from commit 79066dc)

# Conflicts:
#	go.mod
#	go.sum
@mergify mergify bot added conflicts PR is conflict with target branch v1.6.x Release v1.6.x labels Jan 18, 2026
@mergify
Copy link
Contributor Author

mergify bot commented Jan 18, 2026

Cherry-pick of 79066dc has failed:

On branch mergify/bp/release/v1.6/pr-1259
Your branch is up to date with 'origin/release/v1.6'.

You are currently cherry-picking commit 79066dc.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify
Copy link
Contributor Author

mergify bot commented Jan 18, 2026

❗❗❗
All commits in this PR must be signed off.
Please sign all commits by:

git rebase HEAD~1 --signoff
git push --force-with-lease origin mergify/bp/release/v1.6/pr-1259

@mergify mergify bot removed the conflicts PR is conflict with target branch label Jan 18, 2026
@mergify
Copy link
Contributor Author

mergify bot commented Jan 18, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Enforce verified commits

This rule is failing.

Make sure that we have verified commits

  • #commits-unverified = 0

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(\[wip\]|\[backport\]|\[cherry-pick\])?( )?(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 Enforce linear history

Wonderful, this rule succeeded.

Make sure that we have a linear history, no merge commits are allowed

  • linear-history

@github-actions
Copy link

This PR will be closed due to a long period of inactivity. If you would like this PR to remain open then please comment or update.

@github-actions github-actions bot added the stale label Mar 20, 2026
@mergify
Copy link
Contributor Author

mergify bot commented Mar 20, 2026

👋 mergify[bot] your PR is conflicting and needs to be updated to be merged

@mergify mergify bot added the conflicts PR is conflict with target branch label Mar 20, 2026
@github-actions github-actions bot removed the stale label Mar 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conflicts PR is conflict with target branch v1.6.x Release v1.6.x

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants