heavy-duty/cast
7
0
Fork 0
Code Issues 4 Pull requests Projects Releases 3 Packages Wiki Activity Actions

style: apply biome formatting to the step-block extractor

Browse source 
The new findIndex callback and the monoBlock array literal exceeded biome's
line budget, so `biome check --error-on-warnings .` failed and took the build
job red with it. Formatter output applied verbatim; no logic change, and the
extractor mutations still behave (unrelated job gated -> green, monotonic step
gated -> red).

My miss, and the same shape as the shellcheck one on box#144: I tailed two
lines of `npm run check` and never saw "Found 1 error". Ran CI's exact command
and read all of its output this time.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
dan-claude-bot 2026-07-20 21:04:17 +00:00
parent 7022894358
commit 601f6168f5
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
test/release.test.ts
View file

@ -705,11 +705,16 @@ describe("changelog-monotonic.sh — release headings are append-only (#133)", (
/^ {6}- name: no shipped changelog heading/.test(l),
);
const after = ciLines.slice(monoStart + 1);
const monoEnd = after.findIndex((l) => /^ {6}- /.test(l) || /^ {2}\S/.test(l));
const monoEnd = after.findIndex(
(l) => /^ {6}- /.test(l) || /^ {2}\S/.test(l),
);
const monoBlock =
monoStart < 0
? undefined
: [ciLines[monoStart], ...after.slice(0, monoEnd < 0 ? after.length : monoEnd)].join("\n");
: [
ciLines[monoStart],
...after.slice(0, monoEnd < 0 ? after.length : monoEnd),
].join("\n");
expect(monoBlock).toBeDefined();
expect(monoBlock).toContain("changelog-monotonic.sh");
// Anchored: an `if:` inside a `run:` line is not a step condition.