Skip to content
PR Automation

chore(spec)!: raise MIGRATION_SUPPORT_FLOOR from 10 to 16 — upgrades are supported from protocol 16 onward #26916

Sign in to view logs

chore(spec)!: raise MIGRATION_SUPPORT_FLOOR from 10 to 16 — upgrades are supported from protocol 16 onward

chore(spec)!: raise MIGRATION_SUPPORT_FLOOR from 10 to 16 — upgrades are supported from protocol 16 onward #26916

Triggered via pull request September 20, 2026 15:28
@os-steveos-steve
synchronize #19302
claude/issue-19056-migration-support-floor-16
Status Success
Total duration 1m 5s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
16s
Check PR Size
Check Changeset
1m 1s
Check Changeset
Auto Label
8s
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/19056-migration-support-floor-16.md#L0
ADR-0087 exemption (no-migration-prescription): no authorable surface moves: no spec key, export or config field is removed or renamed, so there is no source rewrite for a D2 conversion or a D3 semantic entry to carry, and nothing for `os migrate meta` to rewrite. What narrows is the accepted `fromMajor` ARGUMENT RANGE of `applyMetaMigrations`, which the ledger has no vocabulary for - a conversion rewrites metadata, and this metadata is untouched. The one instruction a stopped consumer needs - reach protocol 16 by another path, then re-run - is carried by the `MigrationFloorError` message itself.
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"