PerishLab/keel
1
0
Fork 0
Code Issues 7 Pull requests Projects Releases Packages Wiki Activity Actions

release: cut 0.10.4 with the authority change written down #164

Merged
PerishFire merged 1 commit from land/release-0-10-4 into main 2026-08-15 11:01:32 +00:00
Conversation 0 Commits 1 Files changed 8 +272 -17
PerishFire commented 2026-08-15 10:58:59 +00:00
Owner
Copy link

release: cut 0.10.4 with the authority change written down

The workspace moves to 0.10.4 and the release carries what a caller has to
know, in both languages: creating a row no longer mints coverage a grant
already carries, a set is authorized by the state it started in, and PATCH
answers 204 rather than 404 when the writer can no longer see what they wrote.

The migration is written for the two shapes that actually break. An operator
whose created rows outlived the grant that let them create — those rows now go
when the grant goes, and if that access was meant to survive it needs an
explicit grant, which is what it always was. And a product that forbade
transfer by leaning on the refusal a hand-over used to get: the engine no
longer refuses it, so the prohibition has to be a grant.

No store changes, and no sweep. Grants minted by earlier versions stay put;
they are redundant now rather than wrong, and an estate can end them as
ordinary rows once it decides it wants to.

AGENTS.md named plumb release dispatch, which plumb 0.19.0 does not have.
Publication is a forge lane, release-exact.yml, and the document now says so
along with the rehearsal switch that publishes nothing.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

release: cut 0.10.4 with the authority change written down The workspace moves to 0.10.4 and the release carries what a caller has to know, in both languages: creating a row no longer mints coverage a grant already carries, a `set` is authorized by the state it started in, and `PATCH` answers 204 rather than 404 when the writer can no longer see what they wrote. The migration is written for the two shapes that actually break. An operator whose created rows outlived the grant that let them create — those rows now go when the grant goes, and if that access was meant to survive it needs an explicit grant, which is what it always was. And a product that forbade transfer by leaning on the refusal a hand-over used to get: the engine no longer refuses it, so the prohibition has to be a grant. No store changes, and no sweep. Grants minted by earlier versions stay put; they are redundant now rather than wrong, and an estate can end them as ordinary rows once it decides it wants to. `AGENTS.md` named `plumb release dispatch`, which plumb 0.19.0 does not have. Publication is a forge lane, `release-exact.yml`, and the document now says so along with the rehearsal switch that publishes nothing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
release: cut 0.10.4 with the authority change written down
All checks were successful
guard / guard (pull_request) Successful in 2m22s
Details
guard / guard (push) Successful in 2m0s
Details
f753b3ee17 
release: cut 0.10.4 with the authority change written down

The workspace moves to 0.10.4 and the release carries what a caller has to
know, in both languages: creating a row no longer mints coverage a grant
already carries, a `set` is authorized by the state it started in, and `PATCH`
answers 204 rather than 404 when the writer can no longer see what they wrote.

The migration is written for the two shapes that actually break. An operator
whose created rows outlived the grant that let them create — those rows now go
when the grant goes, and if that access was meant to survive it needs an
explicit grant, which is what it always was. And a product that forbade
transfer by leaning on the refusal a hand-over used to get: the engine no
longer refuses it, so the prohibition has to be a grant.

No store changes, and no sweep. Grants minted by earlier versions stay put;
they are redundant now rather than wrong, and an estate can end them as
ordinary rows once it decides it wants to.

`AGENTS.md` named `plumb release dispatch`, which plumb 0.19.0 does not have.
Publication is a forge lane, `release-exact.yml`, and the document now says so
along with the rehearsal switch that publishes nothing.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Land-Source: release-0-10-4@10fba73e243b71cb5f0de7d301153d65a2874c25
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
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!164
No description provided.