ci: add flaky-test management (#489)#2
Merged
Conversation
Vitest retry:2 + Playwright retries:2 (CI) to surface flaky tests instead of hard-failing on a transient flake. Also drop the full typecheck+coverage re-run from publish-npm.yml (deploy = build + package + publish only) since the PR's CI gates already tested the exact merged tree (#488 release-blocker). Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stack detected: JS/TS (Vitest + RTL + Playwright, no ESLint config, no Rust).
Pieces applied:
retry: 2intestconfig — a flaky unit/component test retries instead of hard-failing CI.retriesbumped1 -> 2in CI — surfaces flaky e2e/a11y runs.eslintdevDependency), so the RTL lint rules have nothing to attach to; skipped rather than bootstrapping a new lint pipeline as a side effect of this ticket.npm run typecheck+npm run coveragere-run frompublish-npm.yml(tag-triggered). Deploy now only doesnpm ci+npm run build+ publish — the PR's own CI gates (ci.yml: typecheck, coverage ≥80%, e2e+axe) already verified the exact merged tree before the tag existed. Matches #488 (a release-blocking failure was a flaky re-run of tests that had already passed on the PR).release.yml(changelog+tag) does no test re-run — untouched.Version bumped
0.1.3 -> 0.1.4(patch,ci:— no public API change).Test plan
ci.yml) green on this PR (typecheck, coverage ≥80%, e2e+a11y) — GitHub Actions validates, not run locally per instructions.publish-npm.ymlunaffected until next tag (not exercised by this PR; reviewed by inspection).#489
Co-Authored-By: Claude noreply@anthropic.com