Bump jwt from 2.10.1 to 3.2.0 in /demo

[dependabot]

Bumps jwt from 2.10.1 to 3.2.0.

Changelog

Sourced from jwt's changelog.

v3.2.0 (2026-05-13)

Full Changelog

Features:

• Add enforce_hmac_key_length configuration option #716 - (@​304)

Fixes and enhancements:

• Reject nil and empty HMAC keys when signing and verifying (CVE-2026-45363 / GHSA-c32j-vqhx-rx3x)
• Fix compatibility with the openssl 4.0 gem #706
• Test against Ruby 4.0 on CI #707
• Fix type error when header is not a JSON object #715 - (@​304)

v3.1.2 (2025-06-28)

Full Changelog

Fixes and enhancements:

• Avoid using the same digest across calls in JWT::JWA::Ecdsa and JWT::JWA::Rsa #697
• Fix signing with a EC JWK #699 (@​anakinj)

v3.1.1 (2025-06-24)

Full Changelog

Fixes and enhancements:

• Require the algorithm to be provided when signing and verifying tokens using JWKs #695 (@​anakinj)

v3.1.0 (2025-06-23)

Full Changelog

Features:

• Add support for x5t header parameter for X.509 certificate thumbprint verification #669 (@​hieuk09)
• Raise an error if the ECDSA signing or verification key is not an instance of OpenSSL::PKey::EC #688 (@​anakinj)
• Allow OpenSSL::PKey::EC::Point to be used as the verification key in ECDSA #689 (@​anakinj)
• Require claims to have been verified before accessing the JWT::EncodedToken#payload #690 (@​anakinj)
• Support signing and verifying tokens using a JWK #692 (@​anakinj)

v3.0.0 (2025-06-14)

Full Changelog

Breaking changes:

... (truncated)

Commits

• db560b7 Merge commit from fork
• ffef4f2 Bump actions/download-artifact from 7 to 8 (#719)
• 69a343d Bump actions/upload-artifact from 6 to 7 (#718)
• 78e7ed2 Fix Style/PredicateWithKind RuboCop issue (#720)
• 1a1d877 Extract context classes into separate files for better organization (#717)
• d3e52e9 Add enforce_hmac_key_length configuration option (#716)
• 24ec3d8 Fix type error when header is not a JSON object (#715)
• 8c655d4 Fix typo in "Rubocop" to use correct casing "RuboCop" (#714)
• 7af2ac0 Bump actions/download-artifact from 4 to 7 (#708)
• efd5e6f Bump actions/upload-artifact from 4 to 6 (#709)
• 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1c390a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[llastflowers]

@copilot can you analyze the safety of the breaking changes in this PR?

[Copilot]

@copilot can you analyze the safety of the breaking changes in this PR?

I reviewed the bump for /demo and it looks low risk overall:

• The repo has no direct jwt usage in /demo (require 'jwt' / JWT.*), so most JWT 3.x API breaks are unlikely to affect app code directly.
• The lockfile update also moved googleauth to 1.16.2 and signet to 0.21.0; both upstream changelogs explicitly include JWT 3.x support.
• JWT 3.x breaking changes are mostly stricter verification/security behavior (e.g., stricter base64 parsing, stronger key requirements, removed deprecated APIs). Those are good defaults and mainly impact code that used edge/deprecated paths.
• Security-wise, this upgrade is important: jwt 2.10.1 is affected by GHSA-c32j-vqhx-rx3x / CVE-2026-45363 and 3.2.0 is the patched version.

So I’d consider this upgrade safe for this PR, with the usual recommendation to run a quick auth-related smoke test in demo runtime paths.