Repository navigation
CI: skip, don't fail, a check the Fetch API never delivered the change for - #264
Merged
Merged
Conversation
…e for On dev, Repo Push can drop a list reorder or a redirection edit saved while that instance's push holds its lease, and the change never reaches the Fetch API. The v1.3.0 gate failed twice on that with every CLI check passing. These now count as skipped (environment), shown in the summary, and never fail the run: - a wait for the Fetch API that times out (fetch-order, fetch-catch-up, a drift edit's wait); - a later drift:listOrder on a list whose earlier change never showed, which the CLI rightly treats as pending; - a verify whose only differences are list orders the no-op preflight reports as not in the Fetch API yet. Any other error or difference still fails. The README also says to re-run all jobs of a failed publish run: re-running only the failed jobs reuses released leases. Co-Authored-By: Claude Opus 5.5 <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
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.
Harness only (
ci/), no CLI code.The
v1.3.0gate failed twice with every CLI check passing: on dev, Repo Push dropped a list reorder and a redirection edit (saved while that instance's classic push held its lease), so the Fetch API never showed them. These checks now count as skipped (environment), shown with ⏭️ and counted in the summary, and never fail the run:apply:fetch-order,apply:fetch-catch-up, a drift edit's wait);drift:listOrderon a list whose earlier change never showed (the CLI rightly treats it as pending);verifywhose only differences are list orders the no-op preflight reports as "not in the Fetch API yet".Any other error or difference still fails. Replayed against the failed attempt's results: its 5 failures all become skips; the first attempt's 1 failure too.
Also fixes the README: re-run all jobs of a failed publish run (re-running only the failed ones reuses released leases).
The Repo Push side is tracked separately.
🤖 Generated with Claude Code