@@ -16,7 +16,7 @@ export GIT_WORK_TREE="$REPO_ROOT"
1616# ALLOW_BIOME_BUMP=1 git commit ...
1717PINNED_PKG_JSON=" js/package.json"
1818if git diff --cached --name-only --diff-filter=ACM | grep -qx " $PINNED_PKG_JSON " ; then
19- # Pinned: @biomejs/biome → 2.4.15 .
19+ # Pinned: @biomejs/biome → 2.5.0 .
2020 #
2121 # Rationale: biome 2.4.12 through 2.4.16 have a deterministic Rust stack
2222 # overflow on macOS arm64 when running TS-aware nursery rules
@@ -26,12 +26,14 @@ if git diff --cached --name-only --diff-filter=ACM | grep -qx "$PINNED_PKG_JSON"
2626 # 2.4.16 locally on 2026-05-28 and CONFIRMED it still crashes — see
2727 # DataRecce/recce-cloud-infra#1382 for the testing notes.
2828 #
29- # The js/biome.json in this repo does NOT currently enable those rules,
30- # so 2.4.15 is safe here. But a silent dependabot bump past this version
31- # (or a future enabling of those rules) could regress us. Any change
32- # requires deliberate ack. When biome ships a release that confirms the
33- # full fix, update EXPECTED_BIOME in the same commit as the bump.
34- EXPECTED_BIOME=" 2.4.15"
29+ # 2.5.0 is ABOVE the affected 2.4.12–2.4.16 range and verified clean on
30+ # macOS arm64 (`biome check src/` + `packages/ui/src/` exit 0, no stack
31+ # overflow). Bumped to 2.5.0 in #1435; this guard was left at 2.4.15 by
32+ # that PR and reconciled here. The js/biome.json in this repo does NOT
33+ # currently enable those nursery rules either. A silent dependabot bump
34+ # still requires deliberate ack: when changing biome, update EXPECTED_BIOME
35+ # in the same commit as the bump (and re-run the macOS arm64 check above).
36+ EXPECTED_BIOME=" 2.5.0"
3537 # head -1 hardens against a future pnpm.overrides entry adding a second
3638 # "@biomejs/biome": line. Fail-loud (below) if extraction is empty so a
3739 # package.json reformat (or removed dep) can't silently disable the guard.
0 commit comments