Skip to content

Align release coverage gates with CI#67

Merged
iarunsaragadam merged 1 commit into
mainfrom
fix/release-coverage-thresholds
Jun 23, 2026
Merged

Align release coverage gates with CI#67
iarunsaragadam merged 1 commit into
mainfrom
fix/release-coverage-thresholds

Conversation

@iarunsaragadam

Copy link
Copy Markdown
Contributor

The v0.1.0 release failed because release.yml gated internal/ >= 84% / pkg/ >= 88%, while CI (the bar every PR passes) gates internal/ >= 68% / pkg/ >= 65% and measured internal/ coverage is 78.73%. Those release thresholds were never exercised (no release had ever run) and are unmeetable. Align release.yml to the CI standard; the maintained per-package floors (.coverage-gates.yml) are unchanged and still enforced identically in both workflows.

The release workflow gated internal/ >= 84% and pkg/ >= 88%, but CI (the bar
every PR passes) gates internal/ >= 68% and pkg/ >= 65%, and measured internal/
coverage is 78.73%. The stricter release thresholds were never exercised (no
release had been cut) and are unmeetable, so the first v0.1.0 release failed at
the coverage gate. Align release.yml to the CI/.coverage-gates.yml standard; the
maintained per-package floors are unchanged and still enforced in both.
@iarunsaragadam
iarunsaragadam merged commit 68e8748 into main Jun 23, 2026
12 checks passed
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