Repository navigation
Polish platform upgrade and rollback UX - #370
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://codex-platform-maintenance-ux-void-cloud.voidzero-docs.workers.dev (commit 7268417)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Brooooooklyn
force-pushed
the
codex/platform-maintenance-ux
branch
from
October 5, 2026 07:55
aeac8fa to
7268417
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
During platform upgrades and rollbacks, administrators can now follow saved lifecycle progress at
/admin/status. The authenticated page shows source and target versions, phase, timestamps, and the API's independently observed traffic state. It refreshes while visible, preserves the last confirmed snapshot when updates fail, and prompts for sign-in when the session expires.The CLI previews availability impact, saves resumable progress, and prints concrete recovery commands that retain custom runtime paths.
platform status <installation-id>shows the local checkpoint before live discovery. Visitors receive a temporary-unavailability page with a manual retry link; API and mutation requests retain HTTP 503 responses without automatic replay.Existing traffic guards, administrator authentication, Sandbox drain access, and runtime-only rollback behavior remain in place. Completed operations on disabled installations still report paused traffic. The status page requires a reachable API and authentication database; these changes do not guarantee zero downtime.
Documentation and regression coverage cover these workflows. The missing-package resolver regression also runs in native Node so the test runner's workspace resolution cannot mask an uninstalled package.
Validation: