Skip to content

ci: lower the coverage floors and drop the README coverage gate - #48

Merged
nolindnaidoo merged 1 commit into
mainfrom
ci/gate-headroom
Oct 7, 2026
Merged

nolindnaidoo merged 1 commit into
mainfrom
ci/gate-headroom

Conversation

@nolindnaidoo

Copy link
Copy Markdown
Owner

Gives the coverage gates room so an ordinary change cannot trip them.

  • Unit coverage floor: 75 lines / 80 functions / 75 statements become 70 for all three. Branches stay at 60.
  • Crate per-module floor: 75 becomes 70.
  • CI no longer runs the "README coverage section is current" step. It failed whenever a test was added, because the test count must match exactly, and whenever coverage moved by more than a point. The section is regenerated at release, and bun run coverage:readme:check is still there to run by hand.
  • AGENTS.md, CLAUDE.md and the crate documents state the new numbers.

The same change is open in all sixteen extension repos. vitest.config.ts and ci.yml are held byte-identical across them, so these merge together.

Verified locally: lint, typecheck, unit tests with coverage, the agent-files check, and check:fleet and check:doc-paths from the site.

The unit floor moves from 75 lines / 80 functions / 75 statements to 70 for
all three, with branches unchanged at 60. The crate's per-module floor moves
from 75 to 70. Both are backstops against a module nobody tested and sit well
under real coverage, so an ordinary change cannot trip them.

CI no longer checks that the README's Testing section matches a real run.
That step failed a build whenever a test was added, because the test count
must match exactly, and whenever coverage moved by more than a point, on
changes that had nothing wrong with them. The section is regenerated at
release, and coverage:readme:check is still there to run by hand.
@nolindnaidoo
nolindnaidoo merged commit f38dfa8 into main Oct 7, 2026
32 checks passed
@nolindnaidoo
nolindnaidoo deleted the ci/gate-headroom branch October 7, 2026 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant