Skip to content

refactor(metadata,spec)!: retire the adr-0030-notification-event migration — no operator door, no platform invoker #23329

refactor(metadata,spec)!: retire the adr-0030-notification-event migration — no operator door, no platform invoker

refactor(metadata,spec)!: retire the adr-0030-notification-event migration — no operator door, no platform invoker #23329

Triggered via pull request September 9, 2026 15:55
Status Success
Total duration 1m 17s
Artifacts

pr-automation.yml

on: pull_request
Check PR Size
48s
Check PR Size
Check Changeset
53s
Check Changeset
Auto Label
21s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 notice
Check Changeset: .changeset/retire-adr-0030-notification-event-migration.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing authorable moves and nothing is renamed: no spec key, no config field, no stored-metadata shape, and no replacement spelling for anyone to adopt. The removed surfaces are one runtime function on `@objectstack/metadata/migrations`, its three own result/option/receipt types, and one member of a constant tuple — none of which appears in any authorable document, so `objectstack migrate meta` has nothing it could rewrite and a ledger entry would prescribe a rewrite that does not exist. The consumer-side action is a deletion, delivered by the compiler on the import and by the barrel tombstone beside it.