chore: bump jsonwebtoken version from 8 to 9 #2779
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kuruk-mm
changed the title
It uses the latest Ring, which fixes an issue for compiling to wasm32-wasi Issue: briansmith/ring#1043
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It uses the latest Ring, which fixes an issue for compiling to wasm32-wasi
jsonwebtoken 8 uses ring v0.16.20 that has the issue
Issue: briansmith/ring#1043
Motivation
Compiling to wasm32-wasi was failing
Solution
Bump jsonwebtoken to use latest Ring (v0.17.8 now)