-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update module github.com/micahparks/keyfunc to v3 #27
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/github.com-micahparks-keyfunc-3.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
b213dab
to
1e21d6e
Compare
1758c12
to
c3fb8ee
Compare
c3fb8ee
to
e15773d
Compare
e15773d
to
3c12ba8
Compare
3c12ba8
to
bbc6c15
Compare
bbb48fc
to
c376e7b
Compare
c376e7b
to
b109eed
Compare
b109eed
to
f699628
Compare
f699628
to
53979e5
Compare
f72ebab
to
65f85a8
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
65f85a8
to
68bfee0
Compare
68bfee0
to
5a28ea9
Compare
83bffc1
to
36e6495
Compare
36e6495
to
92e72c6
Compare
92e72c6
to
536f4c1
Compare
3cfe4f2
to
f5e4712
Compare
84e1c29
to
f5e4712
Compare
f5e4712
to
d989b4b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 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.
This PR contains the following updates:
v1.9.0
->v3.3.10
Release Notes
MicahParks/keyfunc (github.com/MicahParks/keyfunc)
v3.3.10
Compare Source
v3.3.9
Compare Source
v3.3.8
Compare Source
v3.3.7
Compare Source
v3.3.6
Compare Source
v3.3.5
Compare Source
v3.3.4
Compare Source
v3.3.3
Compare Source
v3.3.2
: Allow for user provided ctx during parseCompare Source
The purpose of this release is to add a new method,
.KeyfuncCtx
.This new method accepts a
context.Context
, then returns ajwt.Keyfunc
. This user providedcontext.Context
is used during JWK lookup in thegithub.com/MicahParks/jwkset
package when parsing JWTs. Passing a request scoped context allows the JWT parsing and JWK retrieval to cancel according to the givencontext.Context
behavior instead of the defaultcontext.Context
, which was provided atkeyfunc.Keyfunc
initialization.In practice, this is used to prevent situations where many JWTs with
kid
not in a remote JWK Set are attempting to be parsed over a long period of time.Relevant issues:
Relevant pull requests:
v3.3.1
Compare Source
v3.3.0
Compare Source
v3.2.9
Compare Source
v3.2.8
Compare Source
v3.2.7
Compare Source
v3.2.6
Compare Source
v3.2.5
Compare Source
v3.2.4
Compare Source
v3.2.3
: Wrap errors where appropriateCompare Source
The purpose of this pull request is to wrap errors with
errors.Join
where appropriate.Relevant issues:
Relevant pull requests:
v3.1.2
: X.509 Thumbprint bug fixCompare Source
JWK Sets have two X.509 thumbprint parameters that are optional. A bug in
github.com/MicahParks/jwkset
made these parameters required in circumstances that affect thekeyfunc
project. This release updates this dependency to the latest version.Thank you, @joshkaplinsky, for reporting this bug!
Please see the below release for details:
https://github.com/MicahParks/jwkset/releases/tag/v0.5.5
v3.1.1
Compare Source
v3.1.0
Compare Source
v3.0.0
: V3 simplify API by using github.com/MicahParks/jwksetCompare Source
This upgrade removes most of the code in this repository and outsources JWK and JWK Set related code to the updated github.com/MicahParks/jwkset package. The exported assets from the keyfunc project has been vastly reduced as well, with the intention of making it easier to use for the majority of use cases.
v2.1.0
: Tolerate initial JWK Set HTTP ErrorCompare Source
The purpose of this release is to add a new feature that allows
keyfunc.Get
to continue without error even if the initial HTTP request to the JWK Set fails. This supports the use case of multiple JWK Sets when a subset are undergoing maintenance, among others.This is done through the new
TolerateInitialJWKHTTPError
field on thekeyfunc.Options
data structure. If the initial HTTP request fails, the resulting*keyfunc.JWKS
will contain no keys, but have the opportunity to be populated by a future background goroutine refresh.Relevant issues:
Relevant pull requests:
v2.0.3
Compare Source
The purpose of this release is to correct a comment and error text.
Relevant pull requests:
v2.0.2
Compare Source
The purpose of this release is to change the limitation for creating a
MultipleJWKS
from requiring 2 or more JWK Set URLs to 1 JWK Set URLs. It appears there was no technical reason for this limitation and it is more convenient to use the Multi JWK Set implementation in some use cases.Related issues:
Related pull requests:
v2.0.1
: Fix bug with context optionCompare Source
The purpose of this pull request is to fix a bug that prevents the
context.Context
passed inkeyfunc.Options
from behaving as described. The described behavior was that the background goroutine would be closed when the context was cancelled, however, the context was immediately overwritten withcontext.Background()
causing its value to be ignored.Thank you to our new contributor @tho!
Related issues:
Related pull requests:
v2.0.0
Compare Source
The purpose of this release is to move support from
[github.com/golang-jwt/jwt/v4](http://github.com/golang-jwt/jwt/v4)
to[github.com/golang-jwt/jwt/v5](http://github.com/golang-jwt/jwt/v5)
.The biggest breaking change is the upstream JWT package version. The other breaking change is that the following deprecated functions have been overwritten by those with the same name plus the
WithOptions
suffix.NewGivenCustom
NewGivenECDSA
NewGivenEdDSA
NewGivenHMAC
NewGivenRSA
If you need to use
[github.com/golang-jwt/jwt/v4](http://github.com/golang-jwt/jwt/v4)
, the last version of this project to support it isv1.9.0
. Should there be a necessary change to this project for/v4
users, it will be located in the separate[github.com/MicahParks/compatibility-keyfunc](http://github.com/MicahParks/compatibility-keyfunc)
project.Relevant pull requests:
Relevant issues:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.