Repository navigation
publish: widen the origin-verify window to 6 min (release propagation lag) - #14
Merged
Merged
Conversation
… lag) The tag trampoline (deploy via workflow_dispatch) works — v0.10.0's dispatch deploy did re-serve — but its Verify step red-flagged a false negative. A release deploys TWICE on the same SHA in quick succession: the merge-to-default-branch push (inline) then the tag trampoline (dispatch). The second (dispatch) re-serve propagates to the origin behind the first, and on 2026-06-25 took ~4 min, past the 60s verify window — so the run failed even though the site went live correctly moments later. Widen the verify poll from 60s to 360s (and slow the interval 1s→5s). The loop still exits the instant the origin matches, so a fast/first-of-SHA deploy isn't slowed; only a genuinely stuck origin now waits the full window before going red. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This branch was previously deployed
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.
What
Widen
publish.yml's origin-Verify poll from 60s → 360s (and slow the interval 1s→5s).Why
Follow-up to #13 (the tag trampoline). On the first real release after merging #13, the trampoline worked — v0.10.0's
workflow_dispatchdeploy re-served and the site went live correctly — but the dispatched run's Verify step went red as a false negative.A release deploys twice on the same SHA in quick succession:
workflow_dispatchThe dispatch (the newest/active deployment) won, but its origin propagation lagged behind the first deploy and only landed at 14:54:56 — ~4 min after the deployment record. Verify gave up at its 60s mark (14:52:26), so the run failed even though the site was correct moments later.
The loop still exits the instant the origin matches, so a fast / first-of-SHA deploy (main, PRs) isn't slowed at all — only a genuinely stuck origin now waits the full window before red-checking. 360s gives ~50% margin over the observed ~4 min.
Test
Next release (merge → tag): the dispatched
publish.ymlrun should now stay green — Verify keeps polling past propagation and matches once the dispatch artifact is live.🤖 Generated with Claude Code