Repository navigation
ci(publish): unit-only publish gate (unblock hung publish) - #12
Merged
Merged
Conversation
The publish workflow's Test step ran full `npm test`, which includes the integration suite (real Chromium + Firefox against live sites). Those tests are local-only — CI has no browser/network guarantee — and hung the publish job indefinitely (~15min on Test vs a ~40s baseline), never reaching the Publish step. ci.yml already runs test:unit only; this aligns publish with it. Browser integration coverage remains local and pre-merge; the adopter-usable-types gate still runs on every publish. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rp7uDDFyQ5qsWHHqDXFjHA
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.
Problem
The v0.20.0 publish (run 33329521340) hung ~15 min on the Test step and never published — vs a ~40s baseline on every prior publish.
Cause
publish.yml's Test step ran fullnpm test, which includes the integration suite — real Chromium + Firefox against live sites. Those are local-only (CI has no browser/network guarantee) and hang indefinitely on the runner.Fix
Test step →
npm run test:unit(fast, deterministic), matching ci.yml (which already runs unit-only). Browser integration coverage stays local + pre-merge; the adopter-usable-types gate still runs on every publish.🤖 Generated with Claude Code