fix: pin jsonwebtoken version to ^1.0.5 #253
Merged
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
|
@israelroldan is attempting to deploy a commit to the Sanity Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@stipsan any chance you could take a look at this one 🙏🏼 (Mentioning you since you approved the one that introduced jsonwebtoken-esm@v2) |
stipsan
changed the title
|
🎉 This PR is included in version 2.0.17 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced Jun 19, 2023
Closed
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.
Fixes #239, #237, #224.
The root cause is that a PR from Renovate (#195) upgraded
jsonwebtoken-esmto v2 which included a breaking change: https://github.com/sanity-io/jsonwebtoken-esm/releases/tag/v2.0.0