Repository navigation
Add stack creation and improve update progress and server switching - #20
Merged
Merged
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
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.
Summary
Add Compose stack creation from the Stacks screen, with a name, Compose YAML and optional
.envcontent. Users can save without starting or create and deploy with pull/build/recreate options. A dedicated progress screen shows real server status and output; deployment retries preserve the already-created stack.Improve container updates and server switching:
Validation
git diff --checkpassed.API compatibility
Requests preserve the selected profile's bearer and custom proxy headers. Container-update polling falls back to the original batch endpoint only when the streaming route returns 404/405; ambiguous failures never repeat the mutation.
Stack-name collision checking and creation cannot be atomic with the current Dockhand API. Another client creating the same name between the fresh listing and POST remains a documented limitation. Creation and deployment require their respective permissions.
Production release preparation
Set the Xcode project and XcodeGen source to 1.7.0 (18). Canonical release metadata for the existing en-US and es-ES locales is in
metadata/version/1.7.0; only What's New differs from the live 1.6.0 metadata. Offline metadata validation passed without errors or warnings. Release notes await the user's explicit review before any App Store Connect upload. This release goes directly to App Store review, without TestFlight distribution; iCloud is deferred.