Skip to content

feat(upgrades): say when a plan has nothing to test it - #501

Merged
dannash100 merged 1 commit into
mainfrom
fix/upgrades-untestable-plan
Aug 19, 2026
Merged

feat(upgrades): say when a plan has nothing to test it#501
dannash100 merged 1 commit into
mainfrom
fix/upgrades-untestable-plan

Conversation

@dannash100

@dannash100 dannash100 commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

No deployment has ever been migration-tested: nothing is declared on a migrating intent, and the page read "not yet tested" as though a result were on its way.

  • Rows say "not set up" when nothing is declared to migrate that group's data.
  • The "testing" chip stops firing on another intent's restore traffic. Issuances carry no intent, so the declaration is the only thing that separates them.

@dannash100
dannash100 marked this pull request as ready for review August 19, 2026 22:25
@dannash100
dannash100 force-pushed the fix/upgrades-untestable-plan branch from 7a43d77 to 4d593c2 Compare August 19, 2026 22:51
@dannash100 dannash100 changed the title feat(upgrades): bound pre-upgrade testing to the fortnight before a plan feat(upgrades): say when a plan has nothing to test it Aug 19, 2026
@dannash100

Copy link
Copy Markdown
Contributor Author

🤖 Screenshots.

Nothing declared to migrate the deployment's data

Same plan with an upgrade replica declared

@dannash100
dannash100 added this pull request to the merge queue Aug 19, 2026
Merged via the queue into main with commit 4957bed Aug 19, 2026
7 checks passed
@dannash100
dannash100 deleted the fix/upgrades-untestable-plan branch August 19, 2026 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant