Skip to content

fix(runtime): key package lifecycle state by project, not by environment alone #22276

fix(runtime): key package lifecycle state by project, not by environment alone

fix(runtime): key package lifecycle state by project, not by environment alone #22276

Triggered via pull request September 7, 2026 10:04
Status Success
Total duration 51s
Artifacts

pr-automation.yml

on: pull_request
Check PR Size
17s
Check PR Size
Check Changeset
47s
Check Changeset
Auto Label
9s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

1 notice
Check Changeset: .changeset/package-state-per-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 changes is the NAME of an operational state file the runtime 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 runtime reads the old name itself while no per-project file exists, so no consumer rewrites anything and there is no authored artifact a metadata upgrader could reach.