Repository navigation
build(deps): bump com.nimbusds:nimbus-jose-jwt from 10.9.1 to 10.10 - #20397
Conversation
Bumps [com.nimbusds:nimbus-jose-jwt](https://bitbucket.org/connect2id/nimbus-jose-jwt) from 10.9.1 to 10.10. - [Changelog](https://bitbucket.org/connect2id/nimbus-jose-jwt/src/master/CHANGELOG.txt) - [Commits](https://bitbucket.org/connect2id/nimbus-jose-jwt/branches/compare/10.10..10.9.1) --- updated-dependencies: - dependency-name: com.nimbusds:nimbus-jose-jwt dependency-version: '10.10' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
FrankChen021
left a comment
There was a problem hiding this comment.
This is an automated review by Codex GPT-5.6 Luna(Max).
Compatibility analysis
Dependency: com.nimbusds:nimbus-jose-jwt, source 10.9.1, target 10.10. The complete published path reviewed in ROUND_1 is 10.9.1 -> 10.10; the published releases in scope are 10.9.1 and 10.10, with no intervening published release. The carried-forward ROUND_1 verdict is SAFE for Druid.
- API/ABI: SAFE. Public and protected symbols used by Druid remain available; 10.10 adds decompression-limit APIs and overloads while retaining prior constructors and methods, with deprecations only.
- Runtime: SAFE for Druid. 10.10 hardens Nimbus compressed-JWE handling, but Druid has no owned
JWEObject,JWEDecrypter,DeflateUtils, or decompression-limit call sites. - Configuration: SAFE. No Druid configuration or new Nimbus option is wired.
- Serialization/wire: SAFE. No Druid schema, JWT contract, wire format, or serialized representation is changed.
- Persistence: SAFE. No persisted data, migration, or storage code is affected.
- Clients: SAFE. No Druid client API or OIDC client contract changes; only the existing validation dependency is upgraded.
- Transitive dependencies: SAFE. The resolved Druid tree selects Nimbus 10.10; pac4j's Nimbus 9.37.3 and oauth2-oidc-sdk's Nimbus 10.9.1 are conflict-omitted. Nimbus's optional BC/Tink metadata updates are not selected by Druid.
- Licenses: SAFE. The target POM remains Apache 2.0; the required Druid license metadata is present for 10.10.
- Extension/plugin SPI: SAFE. Pac4j module registration and Druid extension interfaces are unchanged.
Druid impact
The original PR changes the Nimbus version in extensions-core/druid-pac4j/pom.xml. Druid call sites reviewed were JwtAuthFilter (JWTParser.parse and token validation), Pac4jAuthenticator (OAuth/OIDC client setup), and CustomSSLResourceRetriever (HTTP resource retrieval). No Druid-owned JWE/Deflate implementation, configuration override, persistence path, serialization path, or extension SPI is involved. The only repair files are licenses.yaml (quoted 10.10 metadata) and the dependency metadata; no Java source or test source changed.
Validation
- Maven dependency-tree resolution passed with direct
com.nimbusds:nimbus-jose-jwt:10.10and the expected conflict omissions. - The Apache 2.0 license was verified in the 10.10 POM, and
licenses.yamlparses10.10as a string. git diff --checkpassed.- Public/protected API comparison of 10.9.1 versus 10.10 showed no removed Druid-used symbols; source/JAR inspection showed additive/deprecated compatibility changes.
- The targeted Pac4j validation passed on the final head: 29 tests, 0 failures, 0 errors, 0 skipped.
- The initial packaging failure was repaired by adding the 10.10 license entry, then by quoting
10.10after CI exposed YAML numeric coercion. The eligible unit-timeout rerun was requested once and was superseded by the repair push; no active or deterministic job was rerun.
CI gate
Fresh pre-approval verification for exact head 313c7bb67e721389ca7f774d1d564fff2f81eea6: PR is OPEN, non-draft, MERGEABLE/CLEAN. The statusCheckRollup contains exactly 27 CheckRuns: 27 COMPLETED/SUCCESS, 0 incomplete, 0 failures, and 0 StatusContexts. The commit status endpoint also reports 0 legacy statuses. The isolated worktree is clean and git rev-parse HEAD matches the exact current head.
Automation actions
One native GitHub APPROVE review is being submitted for the exact verified head.
No merge was performed.
Bumps com.nimbusds:nimbus-jose-jwt from 10.9.1 to 10.10.
Changelog
Sourced from com.nimbusds:nimbus-jose-jwt's changelog.
... (truncated)
Commits
e055b3b[maven-release-plugin] prepare for next development iterationc06d769Adds JWEObject.MAX_DECOMPRESSED_PLAIN_TEXT_LENGTH - 10.x WIP (iss #611)a427513Adds explicit non-null checks to DeflateUtils (iss #611)3302e15Fixes potential native memory resource leak in DeflateUtils when Deflater or ...d004e79Optimizes DeflateUtils resource management and memory allocation by guarantee...98ed6baAdjusts JWEObject.MAX_DECOMPRESSED_PLAIN_TEXT_LENGTH to 1 mio bytes (iss #611)0350144Adds MaxDecompressedPlainTextLength implementing JWEDecrypterOption (iss #611)218575fWires MaxDecompressedPlainTextLength (iss #611)3fcb8f5Adds MaxDecompressedPlainTextLength tests for each JWEDecrypter (iss #611)14ae7acAdds CHANGELOG.txt entries (iss #611)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 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)