Repository navigation
chore(deps): bump fast-uri from 3.1.8 to 3.1.9 - #765
Merged
Merged
Conversation
npm audit reports four advisories against fast-uri up to 3.1.8, which fails the lint job's security step.
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #765 +/- ##
=======================================
Coverage 97.67% 97.67%
=======================================
Files 5 5
Lines 1718 1718
Branches 664 664
=======================================
Hits 1678 1678
Misses 39 39
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Summary
The lint job's
npm run securitystep now fails on every branch:npm audit --productionreports four moderate advisories againstfast-uri3.0.0–3.1.8 (GHSA-w74x-v6f9-j3xg, GHSA-xhq7-xmqj-769h, GHSA-wjr9-j795-jxcr, GHSA-333x-w4r6-6crp), reached throughschema-utils→ajv.npm audit fixmoves the lockfile to 3.1.9, and also brings the lockfile's own version up to the 5.13.1package.jsonalready has.What kind of change does this PR introduce?
chore
Did you add tests for your changes?
n/a — lockfile only;
npm run securitypasses.Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
n/a
Use of AI
Claude Code read the failing lint job on #764, ran
npm audit fixand checked that onlyfast-urimoved.Generated by Claude Code