build(deps): bump io.jsonwebtoken:jjwt-api from 0.12.6 to 0.13.0 in /graphwebhook
Bumps io.jsonwebtoken:jjwt-api from 0.12.6 to 0.13.0.
Release notes
Sourced from io.jsonwebtoken:jjwt-api's releases.
0.13.0
This is the last minor JJWT release branch that will support Java 7.
Any necessary emergency bug fixes will be fixed in subsequent
0.13.xpatch releases, but all new development, including Java 8 compatible changes, will be in the next minor (0.14.0) release.All future JJWT major and minor versions (
0.14.0and later) will require Java 8 or later.What's Changed
This release contains a single change:
- The previously private
JacksonDeserializer(ObjectMapper objectMapper, Map<String, Class<?>> claimTypeMap)constructor is nowpublicfor those that want register a claims type converter on their own specifiedObjectMapperinstance. Thank you to@kesrishubham2510for PR #972. See Issue 914.Full Changelog: https://github.com/jwtk/jjwt/compare/0.12.7...0.13.0
0.12.7
This patch release:
Adds a new Maven BOM! This is useful for multi-module projects. See Issue 967.
Allows the
JwtParserBuilderto have empty nested algorithm collections, effectively disabling the parser's associated feature:
- Emptying the
zip()nested collection disables JWT decompression.- Emptying the
sig()nested collection disables JWS mac/signature verification (i.e. all JWSs will be unsupported/rejected).- Emptying either the
enc()orkey()nested collections disables JWE decryption (i.e. all JWEs will be unsupported/rejected)See Issue 996.
Fixes bug 961 where
JwtParserBuildernested collection builders were not correctly replacing algorithms with the same id.Ensures a
JwkSet'skeyscollection is no longer entirely secret/redacted by default. This was an overzealous default that was unnecessarily restrictive; thekeyscollection itself should always be public, and each individual key within should determine which fields should be redacted when printed. See Issue 976.Improves performance slightly by ensuring all
jjwt-apiutility methods that create*Builderinstances (Jwts.builder(),Jwts.parserBuilder(),Jwks.builder(), etc) no longer use reflection.Instead,
staticfactories are created via reflection only once during initialjjwt-apiclassloading, and then*Builders are created via standard instantiation using thenewoperator thereafter. This also benefits certain environments that may not have idealClassLoaderimplementations (e.g. Tomcat in some cases).NOTE: because this changes which classes are loaded via reflection, any environments that must explicitly reference reflective class names (e.g. GraalVM applications) will need to be updated to reflect the new factory class names.
See Issue 988.
Upgrades the Gson dependency to
2.11.0Upgrades the BouncyCastle dependency to
1.78.1New Contributors
@sigpwnedmade their first contribution in jwtk/jjwt#968@TheMrMilchmannmade their first contribution in jwtk/jjwt#979@atanasgmade their first contribution in jwtk/jjwt#974Full Changelog: https://github.com/jwtk/jjwt/compare/0.12.6...0.12.7
Changelog
Sourced from io.jsonwebtoken:jjwt-api's changelog.
0.13.0
This is the last minor JJWT release branch that will support Java 7. Any necessary emergency bug fixes will be fixed in subsequent
0.13.xpatch releases, but all new development, including Java 8 compatible changes, will be in the next minor (0.14.0) release.All future JJWT major and minor versions (
0.14.0and later) will require Java 8 or later.This
0.13.0minor release has only one change:
- The previously private
JacksonDeserializer(ObjectMapper objectMapper, Map<String, Class<?>> claimTypeMap)constructor is nowpublicfor those that want register a claims type converter on their own specifiedObjectMapperinstance. See Issue 914.0.12.7
This patch release:
Adds a new Maven BOM, useful for multi-module projects. See Issue 967.
Allows the
JwtParserBuilderto have empty nested algorithm collections, effectively disabling the parser's associated feature:
- Emptying the
zip()nested collection disables JWT decompression.- Emptying the
sig()nested collection disables JWS mac/signature verification (i.e. all JWSs will be unsupported/rejected).- Emptying either the
enc()orkey()nested collections disables JWE decryption (i.e. all JWEs will be unsupported/rejected)See Issue 996.
Fixes bug 961 where
JwtParserBuildernested collection builders were not correctly replacing algorithms with the same id.Ensures a
JwkSet'skeyscollection is no longer entirely secret/redacted by default. This was an overzealous default that was unnecessarily restrictive; thekeyscollection itself should always be public, and each individual key within should determine which fields should be redacted when printed. See Issue 976.Improves performance slightly by ensuring all
jjwt-apiutility methods that create*Builderinstances (Jwts.builder(),Jwts.parserBuilder(),Jwks.builder(), etc) no longer use reflection.Instead,
staticfactories are created via reflection only once during initialjjwt-apiclassloading, and then*Builders are created via standard instantiation using thenewoperator thereafter. This also benefits certain environments that may not have idealClassLoaderimplementations (e.g. Tomcat in some cases).NOTE: because this changes which classes are loaded via reflection, any environments that must explicitly reference reflective class names (e.g. GraalVM applications) will need to be updated to reflect the new factory class names.
See Issue 988.
Upgrades the Gson dependency to
2.11.0Upgrades the BouncyCastle dependency to
1.78.1
Commits
a757add[maven-release-plugin] prepare release 0.13.0e357463Preparing for the 0.13.0 release.b6f8cb8Made constructor public to allow users their own objectMapper instance (#972)03f088aBumping development version to 0.13.0-SNAPSHOT (#1014)3f2697fRelease 0.12.7 (#1012)efed1cfUpdated 0.12.7 change listca27b12Resolves #1010 (#1011)55c7b9aResolves #771 (#1009)6e9c6a5Bump org.bouncycastle:bcpkix-jdk18on from 1.78 to 1.78.1 (#1008)7ec7dd1Enable JwtParser empty nested algorithm collections. (#1007)- Additional commits viewable 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)