Repository navigation
Add one-call immediate manual service updates - #2
Merged
Merged
Conversation
KyleDerZweite
marked this pull request as ready for review
October 5, 2026 12:37
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.
An authorized manual update currently needs separate discovery, Git publication and apply commands. Add
mooring update SERVICE --nowto publish and deploy the latest allowed stable tag immediately, or--now --version TAGto select an exact higher stable tag in the same repository and semver family.This invocation bypasses the window and release-age delays. Only an exact version overrides the automatic semver level. Bare
update,update --commitandrunretain their behavior; no host configuration or timer changes.One host/maintenance lock covers the operation. Drift, pending operations, unapplied host policy and non-image changes stop publication. A durable receipt pins the digest and prepared Git commit before push. Retries retain that target, pending image-only Git intent takes precedence, and JSON reports publication, deployment phases and actionable recovery. Matching retained approval survives later publication failures. Healthy targets remain unchanged; unknown or different applied bytes require explicit review instead of an implicit same-tag repull.
Closes #1.
Validation for source
13b17357b9b963eff649ca130e4c4f31feaf86b7:docs/validation.md.The subsequent validation commit changes documentation only. GitHub CI checks Python 3.11 and 3.14. The installed Mooring checkout, production services, schedules and credentials were not changed. No merge or production rollout is included.