Skip to content

fix(cli): key the runtime state file by project, not by environment alone #21601

fix(cli): key the runtime state file by project, not by environment alone

fix(cli): key the runtime state file by project, not by environment alone #21601

Triggered via pull request September 5, 2026 20:53
Status Success
Total duration 54s
Artifacts

pr-automation.yml

on: pull_request
Check PR Size
Check PR Size
Check Changeset
49s
Check Changeset
Auto Label
0s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 notice
Check Changeset: .changeset/runtime-state-file-project-key.md#L0
ADR-0087 exemption (no-migration-prescription): Nothing authorable moves: no spec key, export, config field or stored metadata changes spelling or shape, `packages/spec` is untouched, and `objectstack migrate meta` has nothing to rewrite. What is retired is the NAME of a best-effort supervision file that `os serve` writes under the ObjectStack home — a path on disk, not a metadata surface the ledger can project into `spec-changes.json` or the generated upgrade guide. The affected party is an out-of-tree supervisor that opens that path, and the one action it takes is deleting a single stale file; there is no authored artifact for a metadata upgrader to rewrite, and no ledger entry could reach the party that is affected.