ci(publish): skip docs-site-build in PyPI publish preflight - #60
Merged
Conversation
0.8.2 published in ~3 minutes with a lightweight preflight. 0.8.3 swapped public-build-check for phase2-release-preflight, re-running heavy Phase 2 E2E already enforced by PR release-check, stalling the shared publish runner for 30+ min. Restore the lightweight shape for publish (public-preflight-publish = version + audit + sync + test + build/twine check). docs-site stays deploy-pages; Phase 2 stays PR release-check. Drop the now-unneeded chromium step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
AgentArcLab
force-pushed
the
release/public-0.8.3-nodocs
branch
from
September 1, 2026 08:16
2e8b1dd to
b9b94fe
Compare
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.
The publish job ran docs-site-build in parallel with the deploy-pages job, which already builds and deploys the docs site. The two pnpm builds contended on the store and stalled the publish preflight for 30+ minutes with no output. Add
public-preflight-no-docsand use it in the publish workflow so docs validation stays the deploy-pages job's responsibility.🤖 Generated with Claude Code