Repository navigation
Add reviewed Catalog launch and stopped-resource archive workflows - #232
Merged
Merged
Conversation
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.
Catalog discovery and stopped-resource Archive/restore now use the shared typed
command path. A Catalog version can prepare a supported Compose Stack plan;
private answers and exact approval stay in the ordinary console. Launch delegates
to the Catalog/Compose owners and retains live destination and Key checks.
Archive requires fully stopped workloads; restore changes metadata without starting
them. Unsupported templates, external volumes and remaining frontend workflows
remain explicitly pending.
A durable background authorization failure keeps its original operation and
verifiedResult=false. The existing 13-language alert warns about possible partial
changes and avoids blind retries; a late result cannot clear a newer review.
Web Console advances to 1.6.200 and bridge 0.2.2. Lockfile dependency graphs are
unchanged, with version baseline, server handshake and install instructions aligned.
Focused Catalog/Archive/shared-seam/error cases passed before integration, along
with the actual 0.2.2 SDK handshake. Required full CI now executes the affected
Catalog/Archive and shared resource/review cases. Required CI and CodeQL, immutable
publication and designated 8080 browser/role acceptance remain separate gates.
This batch does not complete all 243 frontend business groups; previous tags,
unaffected PASS evidence and original failures remain unchanged.