Repository navigation
fix(deps): update form-data to 4.0.6 - #276
Merged
Merged
Conversation
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
form-datafrom 4.0.5 to 4.0.6, which fixes CRLF injection in multipart field names and filenames (GHSA-hmw2-7cc7-3qxx).hasownto 2.0.4 to satisfy form-data's actual published dependency metadata. Keep the existing compatiblemime-types2.1.35 resolution.desktop/package-lock.json. Preserve the jschardet clean-install resolution from fix(deps): restore jschardet resolution for npm ci #275; no manifest, application code, registry or script-policy changes.Validation
npm ciwith a fresh cache, including the root postinstall, and a separate normal renderernpm ci: passed; both lockfiles stayed unchanged during installation.git diff --check: passed.Existing validation limits