Skip to content
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 dependency aws-jwt-verify to v5 #1183

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
aws-jwt-verify ^3.4.0 || ^4.0.0 -> ^3.4.0 || ^4.0.0 || ^5.0.0 age adoption passing confidence
aws-jwt-verify ^4.0.0 -> ^5.0.0 age adoption passing confidence

Release Notes

awslabs/aws-jwt-verify (aws-jwt-verify)

v5.0.0

Compare Source

Notable new features in v5.0.0:
  • Support for ECDSA and EdDSA algorithms:
  • Allow padding characters (even though non-standard) so e.g. AWS ALB JWTs can be verified with this library (however work is still underway to make that easier still, see #​176 )
  • The default response timeout of the JWKS fetcher was increased from 1500 ms. to 3000 ms. because multiple users reported the previous 1500 ms. being too low--they were hitting timeouts too often. We believe the 3000 ms. is a better, more reasonable, default value.
Breaking changes

This release includes breaking changes, hence moving to major version 5.0.0:

  • Dropped support for Node.js 14, now 16 is the minimum.
  • The fetchJson interface was changed and renamed to fetch. Thus the JsonFetcher was renamed to Fetcher, and corresponding changes were made in the SimpleJwksCache see #​167. So, this affects users who were using the SimpleJsonFetcher, potentially to increase the response timeout (maybe that's no longer needed now, as we raised the default value from 1500 ms. to 3000 ms.).
  • It is now allowed to use an explicit null as issuer. This would throw JwtInvalidIssuerError before, see #​183. This affects users who were counting on null issuer throwing JwtInvalidIssuerError. It is expected that this is rare and the handling of undefined remains unchanged. But if you did depend on the prior behavior (we can't see why you would but who knows), you're affected, and will need to guard against passing a null issuer, if you don't want to allow that, yourself.
What's Changed

Full Changelog: awslabs/aws-jwt-verify@v4.0.1...v5.0.0


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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from 0c74a06 to 65a45f6 Compare January 11, 2025 01:22
@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from 65a45f6 to 7542728 Compare January 11, 2025 06:26
@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from 7542728 to ff4f8d2 Compare January 11, 2025 10:18
@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from ff4f8d2 to ee07a26 Compare January 12, 2025 01:37
@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from ee07a26 to 31453e2 Compare January 13, 2025 20:33
@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from 31453e2 to df28cc4 Compare January 14, 2025 00:59
@renovate renovate bot force-pushed the renovate/aws-jwt-verify-5.x branch from df28cc4 to aa4c57c Compare January 14, 2025 04:18
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.

0 participants