Fix release consumer workflow dispatch contract - #27
Merged
Merged
Conversation
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.
Final release-blocker fix discovered by live GitHub dispatch preflight.
GitHub rejected
.github/workflows/consumer-pin-verification.ymlwith HTTP 422 (Workflow does not have 'workflow_dispatch' trigger) becausefastapi_refandexpress_refomitted the requiredtypefield. This made the seven-workflow release-authority contract impossible to execute despite the YAML text containingworkflow_dispatch.This PR:
type: stringto both missing inputs;workflow_dispatchinput to declare a supported explicit type;The current candidate
40fefb4de8b59978fa338fc09d3a185d5708bc1fis superseded by this fix and must not be tagged. After merge, the full exact-head pre-tag matrix and both consumer pins must be repeated on the new SHA.