Skip to content

[v3 migration 4/4] Verify the migrated release path inside the next real RC window #9500

Description

@os-project-manager

Sub-issue of #9465.

Blocked-by: #9498

Restart-when: .changeset/pre.json exists on origin/main with "mode": "pre" — i.e. the next RC window has been entered.

On hold by design, not by neglect. Everything #9497 and #9498 measure happens in a throwaway clone or on a PR; the behaviour this epic exists to protect — a real cut, over a real accumulated changeset set, under the enforced cut-rc.yml allowlist — only exists inside a genuine pre-mode window. A migration that is green on a PR and wrong at cut time is exactly the failure mode we are buying insurance against, so the insurance is not claimed until it is testable.

What to check when it fires

Non-goals

This card observes a release window; it does not create one. No pre-mode entry or exit, no publish, no tags, no release-workflow dispatch. If something is wrong, the deliverable is a precise report plus a fix card — not a hot fix applied mid-cut.

Acceptance

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions