ci: route the Cargo family through the Cargo-only lane #157

Merged

PerishFire merged 1 commit from land/cargo-only-release-caller into main 2026-08-05 13:33:15 +00:00

Conversation 0 Commits 1 Files changed 1 +7 -1

PerishFire commented 2026-08-05 13:30:42 +00:00

Owner

Copy link

ci: route the Cargo family through the Cargo-only lane

keel declares five lib-only crates and no binaries, so release-binary's
coordinate job waited forever on a target matrix that resolves to an empty
include. That is why the wrapperless caller has never published: its first run
died in freeze on the Cargo-family bug, and its second reached the empty matrix
and blocked.

release-cargo keeps the frozen release inputs, the canonical guard evidence and
the stable changelog law, and drops the binary machine keel has no use for.
The caller keeps its filename so the skeleton still recognises the lane, and
gains the same publish switch the package lane already offers, defaulting to a
rehearsal that mutates nothing.

ci: route the Cargo family through the Cargo-only lane keel declares five lib-only crates and no binaries, so release-binary's coordinate job waited forever on a target matrix that resolves to an empty include. That is why the wrapperless caller has never published: its first run died in freeze on the Cargo-family bug, and its second reached the empty matrix and blocked. release-cargo keeps the frozen release inputs, the canonical guard evidence and the stable changelog law, and drops the binary machine keel has no use for. The caller keeps its filename so the skeleton still recognises the lane, and gains the same publish switch the package lane already offers, defaulting to a rehearsal that mutates nothing.

PerishFire added 1 commit 2026-08-05 13:30:42 +00:00

ci: route the Cargo family through the Cargo-only lane ... e14db2621a

ci: route the Cargo family through the Cargo-only lane

keel declares five lib-only crates and no binaries, so release-binary's
coordinate job waited forever on a target matrix that resolves to an empty
include. That is why the wrapperless caller has never published: its first run
died in freeze on the Cargo-family bug, and its second reached the empty matrix
and blocked.

release-cargo keeps the frozen release inputs, the canonical guard evidence and
the stable changelog law, and drops the binary machine keel has no use for.
The caller keeps its filename so the skeleton still recognises the lane, and
gains the same publish switch the package lane already offers, defaulting to a
rehearsal that mutates nothing.

Land-Source: cargo-only-release-caller@f9f5c84aa2942d87dbd047e269ce7b524fa766a6

PerishFire merged commit e14db2621a into main 2026-08-05 13:33:15 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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

PerishLab/keel!157

No description provided.