Skip to content

chore(deps): bump prometheus/common from 0.67.2 to 0.67.3#17556

Closed
JorTurFer wants to merge 1 commit intoprometheus:mainfrom
JorTurFer:bump-common
Closed

chore(deps): bump prometheus/common from 0.67.2 to 0.67.3#17556
JorTurFer wants to merge 1 commit intoprometheus:mainfrom
JorTurFer:bump-common

Conversation

@JorTurFer
Copy link
Contributor

@JorTurFer JorTurFer commented Nov 19, 2025 •
edited
Loading

Which issue(s) does the PR fix:

This PR bumps common to propagate the support for JWT Authentication for Authorization Grant (RFC 7523 3.1) as alternative to static client credentials.

Does this PR introduce a user-facing change?

[FEATURE] OAuth2: support jwt-bearer grant-type (RFC7523 3.1)

@JorTurFer
[chore]: bump common dep to support RFC7523 3.1
4018611 
Signed-off-by: Jorge Turrado <jorge.turrado@mail.schwarz>
@JorTurFer JorTurFer changed the title [chore]: bump common dep to support RFC7523 3.1 chore(deps): bump prometheus/common from 0.67.2 to 0.67.3 Nov 19, 2025
SuperQ
SuperQ approved these changes Nov 20, 2025
View reviewed changes
Copy link
Member

@SuperQ SuperQ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CC @jan--f, we should pick this in into v3.8.

@JorTurFer
Copy link
Contributor Author

JorTurFer commented Nov 20, 2025

I'll update again this PR if a new version is shipped with this commit -> prometheus/common@04686b2

@jan--f
Copy link
Contributor

jan--f commented Nov 20, 2025

I'll change the target branch to release-3.8 then for easier branch syncing.

@jan--f jan--f changed the base branch from main to release-3.8 November 20, 2025 14:15
@jan--f jan--f changed the base branch from release-3.8 to main November 20, 2025 14:16
@jan--f
Copy link
Contributor

jan--f commented Nov 20, 2025

I'll change the target branch to release-3.8 then for easier branch syncing.

Actually @JorTurFer mind rebasing this on release-3.8.

@JorTurFer
Copy link
Contributor Author

JorTurFer commented Nov 20, 2025

I'll change the target branch to release-3.8 then for easier branch syncing.

Actually @JorTurFer mind rebasing this on release-3.8.

If you want, as soon as the common release is ready, I can bump into both branches, I'm willing to open another PR pointing to 3.8 and pinging you there

@jan--f
Copy link
Contributor

jan--f commented Nov 20, 2025

Only into release-3.8 would be better. I'll sync back the release branch to main anyway. Just looking to deal with as few conflicts as possible :)

@JorTurFer JorTurFer changed the base branch from main to release-3.8 November 20, 2025 15:03
@JorTurFer JorTurFer changed the base branch from release-3.8 to main November 20, 2025 15:03
@JorTurFer
Copy link
Contributor Author

JorTurFer commented Nov 20, 2025

just to be sure, instead of opening a PR from main to main, doing it from 3.8 to 3.8 only, right?

@jan--f
Copy link
Contributor

jan--f commented Nov 20, 2025

just to be sure, instead of opening a PR from main to main, doing it from 3.8 to 3.8 only, right?

Yes that would be my preference :)

@jan--f jan--f mentioned this pull request Nov 21, 2025
Merged
@JorTurFer
Copy link
Contributor Author

JorTurFer commented Dec 2, 2025

Not needed anymore, closed

@JorTurFer JorTurFer closed this Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@SuperQ SuperQ SuperQ approved these changes

@roidelapluie roidelapluie Awaiting requested review from roidelapluie

@jesusvazquez jesusvazquez Awaiting requested review from jesusvazquez

@aknuds1 aknuds1 Awaiting requested review from aknuds1

@cstyan cstyan Awaiting requested review from cstyan

@bwplotka bwplotka Awaiting requested review from bwplotka

@tomwilkie tomwilkie Awaiting requested review from tomwilkie

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@JorTurFer @jan--f @SuperQ