Repository navigation
deploy: pin verified c132e9f2 images [skip deploy] - #177
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
2 participants
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.
Pins the four production Compose projects to the verified c132e9f images published by successful workflow39021671896. The diff contains only five image-reference changes; application source, resource routing and configuration are unchanged.
All four Compose projects passed
docker compose config --quietwith existing production variables injected in memory. The exact image source passed release, Web, Server, Open Notebook, deployment-contract and integration checks. PR checks verify the pin-only diff. A local contract attempt in the new worktree could not load dependencies; it is not counted as a passing check.The commit uses the existing skip-deploy mechanism to keep source admission separate from the explicitly authorized manual Komodo rollout. Operators will drain both old workers, verify schema11 provenance/no live leases, and run
lingxiloop-production-rolloutthrough the txy3-backed API. Product backup/isolated restore update6ad341d1e06d5e1f798295a8 succeeded with all162 table counts matching. No account/login/model test is a release gate under the latest user instruction; those checks remain unverified.