Skip to content

Support jwt gem 3.x alongside 2.x#726

Open
dan98765 wants to merge 1 commit intoauth0:masterfrom
dan98765:support-jwt-3
Open

Support jwt gem 3.x alongside 2.x#726
dan98765 wants to merge 1 commit intoauth0:masterfrom
dan98765:support-jwt-3

Conversation

@dan98765
Copy link
Copy Markdown

@dan98765 dan98765 commented May 5, 2026

Changes

Widens the jwt runtime dependency from ~> 2.7 (which caps at < 3.0) to >= 2.7, < 4.0. This lets consumers that depend on both auth0 and a gem requiring jwt 3.x (e.g. workos >= 6.0) resolve without conflicts.

No code changes — just the gemspec constraint and the lockfile.

References

Testing

Ran the full test suite (bundle exec rake test) on Ruby 3.3.9 with jwt 3.1.2 resolved:

  • 1040 unit examples, 0 failures
  • 164 integration examples, 0 failures (1 pending — pre-existing)
  • Line coverage: 99.56%

No new tests needed since this is a dependency constraint change and all existing JWT-related tests already pass against 3.x.

  • This change adds unit test coverage
  • This change adds integration test coverage
  • This change has been tested on the latest version of Ruby

Checklist

  • I have read the Auth0 general contribution guidelines
  • I have read the Auth0 Code of Conduct
  • All existing and new tests complete without errors
  • Rubocop passes on all added/modified files (note: rubocop fails to start due to a pre-existing config issue in .rubocop_todo.ymlMetrics/LineLength renamed to Layout/LineLength — unrelated to this change)
  • All active GitHub checks have passed

@dan98765 dan98765 requested a review from a team as a code owner May 5, 2026 17:44
@dan98765 dan98765 mentioned this pull request May 5, 2026
5 tasks
Widen the jwt dependency from `~> 2.7` (which caps at < 3.0) to
`>= 2.7, < 4.0`.  This allows consumers that depend on both auth0 and
a gem requiring jwt 3.x (e.g. workos >= 6.0) to resolve without
conflicts.

Full test suite (1040 unit + 164 integration examples) passes on
jwt 3.1.2 / Ruby 3.3.9 with zero failures.

Closes auth0#690
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant