release: actionable activation errors (MCP-16) - #57
Merged
Merged
Conversation
Cover backend error details, metadata review, pending retries, active status refresh, cache invalidation, and release/project isolation so failed activations stay actionable.
Surface server activation errors in accessible row alerts, clear stale errors on retry, and guide readiness failures into MCP metadata review. Reset local state across project navigation while preserving successful activation cache refreshes.
Exercise a deferred metadata lookup through project navigation so an old release cannot reopen dialogs or write deep-link state after its project unmounts.
Prevent a delayed metadata lookup from opening a stale dialog or replacing the new project's URL after the release table unmounts.
…n-errors fix: show actionable release activation errors (MCP-16)
This branch was previously deployed
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
1 participant
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.
Release MCP-16: show actionable activation failures beside the affected release, offer metadata review for readiness failures, and clear stale errors on retry. Release/project isolation also prevents delayed metadata lookups from navigating back to a previous project.
The diff contains only the release table and nine regression tests. Backend activation guards are unchanged; there are no migrations.
Validation: implementation PR #56 passed full hosted CI and independent review. Locally, 191 frontend tests/lint/types/build and 217 Swift tests/release build with warnings as errors passed. Rendered local browser checks with isolated API fixtures verified rejection, metadata review, retry clearing, and successful Active refresh.
Development merged revision: 8fd2ec6. Merged-head CI 36661555584 and promotion CI 36661602904 passed. Development Web deployment 01b377e5-a2dc-49a9-b49a-14a645950051 succeeded at this exact revision.
Authenticated deployed dashboard acceptance passed using tab-local synthetic release/activation responses: 400 → visible backend reason → metadata review dialog → retry clears the error while pending → 204/refetch shows Active. The API fixtures were removed and the real active release 5449D7D5-FA5F-4730-AB05-3C02690D3958 was confirmed unchanged. Console warnings were limited to expired sign-in before reauthentication and the intentional 400; no unexpected UI errors. No stored metadata or release state was changed by these cases.
All promotion checks are green. Awaiting separate user approval before merging to main and triggering Production deployment.
Refs MCP-16; implementation #56.