fix(deps): update dependency aws-jwt-verify to v5 #1183
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.4.0 || ^4.0.0
->^3.4.0 || ^4.0.0 || ^5.0.0
^4.0.0
->^5.0.0
Release Notes
awslabs/aws-jwt-verify (aws-jwt-verify)
v5.0.0
Compare Source
Notable new features in v5.0.0:
Ed25519
Breaking changes
This release includes breaking changes, hence moving to major version 5.0.0:
JsonFetcher
was renamed toFetcher
, and corresponding changes were made in theSimpleJwksCache
see #167. So, this affects users who were using theSimpleJsonFetcher
, 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.).null
as issuer. This would throwJwtInvalidIssuerError
before, see #183. This affects users who were counting onnull
issuer throwingJwtInvalidIssuerError
. It is expected that this is rare and the handling ofundefined
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 anull
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.
This PR was generated by Mend Renovate. View the repository job log.