Skip to content

fix(metadata-protocol)!: an item's lock is the strictest lock among the stored rows in scope for its address (#21761) #30851

fix(metadata-protocol)!: an item's lock is the strictest lock among the stored rows in scope for its address (#21761)

fix(metadata-protocol)!: an item's lock is the strictest lock among the stored rows in scope for its address (#21761) #30851

Triggered via pull request October 5, 2026 02:03
Status Success
Total duration 1m 11s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
22s
Check PR Size
Check Changeset
1m 7s
Check Changeset
Auto Label
21s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

4 notices
Check PR Size
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Auto Label
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Check Changeset: .changeset/21761-lock-address-selection.md#L0
ADR-0087 exemption (no-migration-prescription): the write doors refuse, by the strictest lock among the stored rows in scope, writes they used to admit when the store returned a looser row first. No authorable key, spelling, export or stored shape moves: every stored row keeps parsing, nothing is read or rewritten at rest, and which row an administrator meant to lock is not something a ledger entry can rewrite. The other categories are closed on facts: the package publishes (not unpublished); no ADR-0087 id covers the lock gate (not already-registered); and the change is a door verdict, not a declaration (not runtime-interface-only or type-surface-only).
Check Changeset
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"