Repository navigation
chore: run npm audit fix - #341
Merged
Merged
Conversation
Lockfile-only update within existing package.json ranges. Supersedes the open Dependabot bumps for js-yaml, minimatch, picomatch, node-forge, brace-expansion, lodash, fast-xml-parser, protobufjs and qs.
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
IzaakGough
marked this pull request as ready for review
October 14, 2026 15:39
wandamora
approved these changes
Oct 16, 2026
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.
Replaces #284, #294, #296, #297, #298, #299, #301, #308 and #313.
npm auditreported 84 findings, 5 of them critical, spread across nine Dependabot PRs.This runs
npm audit fixwithout--force, bringing the count to 50 findings with 1 critical.^4.18.1. It is the only runtime dependency affected, and users only get the fix if the published range moves.Unit tests, lint and the Firestore emulator integration suite pass locally on Node 24.