docs: document the retry-until shim input#44
Merged
Conversation
publish.yml's re-dispatch job (v0.22.0) always re-fires the consumer's publish-dispatch.yml shim with -f retry-until=..., but none of the consumer-facing docs (reference/workflows.md's input table, the tutorial's copy-paste shim, CLAUDE.md's consuming snippet) showed it. A shim copied before v0.22.0 is missing the input, which breaks every tagged release's re-dispatch, not just the wedged-origin retry path.
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
publish.yml'sre-dispatchjob (added in v0.22.0, fix: auto-retry via fresh dispatch when the Pages origin wedges #43) always re-fires the consumer'spublish-dispatch.ymlshim with-f retry-until=..., but none of the consumer-facing docs mentioned it — thereference/workflows.mdinput table, the tutorial's copy-paste shim snippet, andCLAUDE.md's "consuming this in another repo" snippet all still only showedpr.retry-untilinput, which breaks there-dispatchjob for every tagged release (not just the wedged-origin retry path it exists for) — found this while bumping a consumer repo's pin to v0.22.0.retry-untilto all three doc surfaces, matching this repo's own dogfoodedpublish-dispatch.yml.Test plan
npm run docsbuilds clean (strict mode, 12 pages, no errors)