release: advance keel to 0.10.3 #158

Merged
PerishFire merged 1 commit from land/advance-to-0-10-3 into main 2026-08-05 15:50:26 +00:00
Owner

release: advance keel to 0.10.3

0.10.2 went out on 31 July through the Runseal wrapper, three days before
that path was retired. The wrapperless caller that replaced it has never
completed a publish: its first attempt died on a Cargo bug in stable Plumb,
its second on an empty build matrix, its third on an absent registry
credential, and its fourth was correctly refused because 0.10.2-beta.1 is a
prerelease of a version already public.

Release continuity on the current path is therefore unproven, and the cheapest
honest proof is a real exact candidate. This advances the family so that
0.10.3-beta.1 becomes a legal target: an immutable validation candidate that
moves no stable consensus and occupies no default seat. It also carries the
one unpublished product change, the declared relation closure.

release: advance keel to 0.10.3 0.10.2 went out on 31 July through the Runseal wrapper, three days before that path was retired. The wrapperless caller that replaced it has never completed a publish: its first attempt died on a Cargo bug in stable Plumb, its second on an empty build matrix, its third on an absent registry credential, and its fourth was correctly refused because 0.10.2-beta.1 is a prerelease of a version already public. Release continuity on the current path is therefore unproven, and the cheapest honest proof is a real exact candidate. This advances the family so that 0.10.3-beta.1 becomes a legal target: an immutable validation candidate that moves no stable consensus and occupies no default seat. It also carries the one unpublished product change, the declared relation closure.
release: advance keel to 0.10.3
All checks were successful
guard / guard (pull_request) Successful in 2m14s
guard / guard (push) Successful in 1m53s
00d1ae0704
release: advance keel to 0.10.3

0.10.2 went out on 31 July through the Runseal wrapper, three days before
that path was retired. The wrapperless caller that replaced it has never
completed a publish: its first attempt died on a Cargo bug in stable Plumb,
its second on an empty build matrix, its third on an absent registry
credential, and its fourth was correctly refused because 0.10.2-beta.1 is a
prerelease of a version already public.

Release continuity on the current path is therefore unproven, and the cheapest
honest proof is a real exact candidate. This advances the family so that
0.10.3-beta.1 becomes a legal target: an immutable validation candidate that
moves no stable consensus and occupies no default seat. It also carries the
one unpublished product change, the declared relation closure.

Land-Source: advance-to-0-10-3@a695121d05ae66428c365db58c922df231c2e3f5
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
PerishLab/keel!158
No description provided.