Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or 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
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.
Change
Update the
fast-urilock entry from3.1.8to3.1.9for the advisory ranges confirmed in GHSA-wjr9-j795-jxcr and GHSA-w74x-v6f9-j3xg. Ajv 8.20.0 already permits^3.0.1and the lock entry remains dev-only. This is one part of #444.Verification
package-lock.json.fast-uri3.1.9, and checked that a relative JSON Schema reference resolves and accepts/rejects the expected inputs.fast-urilock entry.CI dependency
build-check-testfails on the samedeprecation.test.tsTS2835 error seen onmain. This PR's run and the main run show the same failure. Merge #468 first, then merge the updatedmaininto this branch and rerun the checks.