[chore]: bump common dep to support RFC7523 3.1 #17592
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jorge Turrado <[email protected]>
Contributor
Author
|
This is #17556 targetting |
Contributor
Author
|
cc @JorTurFer |
SuperQ
approved these changes
Nov 21, 2025
Contributor
|
I'd wait till this is merged and shipped as release -> prometheus/common#865 |
Contributor
|
or at least, shipping this commit -> prometheus/common@04686b2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?