Skip to content
This repository was archived by the owner on Oct 26, 2026. It is now read-only.

Update braces to 3.0.3 - #23

Closed
MelvinBot wants to merge 1 commit into
Expensify:mainfrom
MelvinBot:claude-updateBraces
Closed

MelvinBot wants to merge 1 commit into
Expensify:mainfrom
MelvinBot:claude-updateBraces

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Details

Bumps braces 3.0.2 → 3.0.3 (and its dep fill-range 7.0.1 → 7.1.1) in package-lock.json to fix the open Dependabot alerts (GHSA-grv7-fg5c-xmjg, uncontrolled resource consumption). Lockfile-only; both versions satisfy the existing ranges.

Usage: Transitive, dev-only. Not imported by src/ and not shipped in the published package. Pulled in by:

  • @babel/cli → chokidar (only for babel --watch)
  • react-native (dev peer) → @react-native/codegen → jscodeshift → micromatch
Change Log

braces 3.0.3:

  • Fix vulnerability (SNYK-JS-BRACES-6838727): stop infinite loop on imbalanced braces
  • Add maxSymbols option to limit input
  • Update eslint, fix unit tests, docs

fill-range 7.1.1:

  • Pass maxLen down to handle zero-padding
  • Update eslint, lint

Related Issues

$ https://github.com/Expensify/Expensify/issues/695864

Manual Tests

  1. npm ci → succeeds; npm ls braces shows only 3.0.3.
  2. npm run ts and npx eslint src → no errors.
  3. npm run build → dist/ builds.
  4. npm audit → no braces advisory.

No new tests: lockfile-only change to dev tooling.

Linked PRs

None.

@github-actions

Copy link
Copy Markdown
Contributor


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@chiragsalian

Copy link
Copy Markdown

Archiving this repository so closing out this PR

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants