[MariaHCD]

Explanation of Change

The open braces Dependabot alerts point to example/yarn.lock, which resolves braces to 2.3.2 (via micromatch@3) and 3.0.2 (via micromatch@4). The fix is in 3.0.3, and there is no patched 2.x release.

This adds a braces: ^3.0.3 resolution to the example app, so both paths resolve to 3.0.3. It also bumps fill-range to 7.1.1 and removes lock entries that only braces 2.x used (fill-range@4, to-regex-range@2, repeat-element, repeat-string, snapdragon-node, snapdragon-util). Only the example app is affected. The library itself has no dependencies.

micromatch@3 now gets braces 3.x, which is outside its requested ^2.3.1 range. I ran micromatch 3.1.10 with braces 2.3.2 and then with 3.0.3 against common globs: brace lists, numeric ranges, negation, **, isMatch, makeRe, braces and any. The results were identical.

Fixed Issues

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

Tests

1. In example/, run yarn install --frozen-lockfile --ignore-scripts.
2. Run yarn why braces and check that the only version is 3.0.3.

Verified with Yarn 1.22.22: the frozen-lockfile install succeeds, and yarn why braces reports only braces@3.0.3, used by every micromatch consumer (anymatch, sane, and Metro's jest-haste-map).

🤖 Generated with Claude Code

https://claude.ai/code/session_01QqAbYSeeLRcFL18iy8t9DC

[MariaHCD]

Closing as superseded by #343. The React Native 0.88 upgrade rebuilt example/yarn.lock, and master now resolves only braces@3.0.3 (via micromatch@4.0.8) with fill-range@7.1.1. Nothing depends on braces 2.x any more, so the resolution this PR adds is no longer needed.