Stop the release callers requiring inputs the dispatcher stopped sending #82

Merged
PerishFire merged 1 commit from concord-member-addressing into main 2026-08-16 10:37:02 +00:00
Owner

Current Plumb reads channel and version from the ref and sends no inputs for an exact release, while both callers still declared them required. Both now match the shape Plumb dispatches.

Current Plumb reads channel and version from the ref and sends no inputs for an exact release, while both callers still declared them required. Both now match the shape Plumb dispatches.
Stop the release callers requiring inputs the dispatcher stopped sending
All checks were successful
guard / guard (pull_request) Successful in 2m20s
guard / windows (pull_request) Successful in 3m23s
guard / guard (push) Successful in 2m22s
guard / windows (push) Successful in 3m45s
47200bd4c8
`plumb ship binary dispatch --version v0.12.8-beta.1` refused with `input
required for 'Exact non-stable version'` before it reached Forgejo. Current
Plumb reads channel and version from the ref and sends no inputs for an exact
release, while both callers still declared them `required: true` and the stable
caller still forwarded a `version` the shared lane ignores.

The shared workflow has carried "Ignored; the version is read from the ref. Stop
passing it." for two minor versions. Nothing here read that, so the callers had
drifted into refusing every dispatch the installed binary can make, and the
first reader was a release that could not start.

Both callers now match the shape Plumb dispatches: `release-exact` takes no
input at all, and `release-stable` takes only the promotion pair.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishFire/concord!82
No description provided.