Repository navigation
deploy: pin passive-bootstrap Worker image [skip deploy] - #182
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.
Pin only the two Worker services to the startup-order fix in e1fe01c. Web and migration services remain on the verified c132e9f image, preserving the existing schema 12 release while recovering the background runners.
Main workflow 39027991893 passed server checks/integration and published the immutable image. Registry index digest: sha256:60d880d61735a7ba0185cd2b7f7d3b6573d5fa7fe8df3eee5a28761e6eb9af78. Both Compose files validate using existing production variables held only in memory; all 22 deployment checks pass, including validation of all seven full-SHA image references. The existing image updater already replaces every server reference on future releases.
Worker recovery uses Komodo service updates after schema 12/runtime 3.5.2 and zero-live-lease verification, followed by actual health/image checks and assertions that unrelated application containers remain unchanged. No database rollback or reset is involved.