Repository navigation
Build exact merged Lazurio proxy containers for server rollout - #3
Merged
Merged
Conversation
|
This pull request targeted The base branch has been automatically changed to |
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
1 participant
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.
The fixed Claude proxy already runs on the MacBook, but this fork has no container publication path for the existing Linux services pools. The upstream Docker workflow publishes to an unrelated Docker Hub namespace. This adds a manually dispatched Linux amd64 build of an exact commit already in this repository's main history, using repository-scoped GHCR permission and recording its digest for Machines qualification.
Status: ready for review.
The workflow validates inputs, does not refresh source data during the build, does not publish
latest, and does not include account/configuration data. The upstream dev-retarget workflow now runs only in router-for-me/CLIProxyAPI, so the fork retains main as its review/publication branch. Other upstream workflows remain unchanged. Deployment uses an immutable digest after qualification; package visibility and each Machine's reviewed Plan/Permit are separate requirements.Validation: actionlint 1.7.7 passed. The exact fixed source built successfully for Linux amd64. Synthetic Linux regression tests passed for Claude executor refresh bindings, thread recovery and quota/cooldown handling in sdk/cliproxy, sdk/cliproxy/auth and internal/runtime/executor. No production OAuth credentials were used.
Work context: DEV-6625, owned by HumanAndMachine-ai Mission Control (private plan). Codex chat
01a1415a-3097-7fd0-b658-6618117744c8, Matěj's MacBook; worktree.worktrees/root/DEV-6625-organization-server-ai-pool, branchcodex/DEV-6625-publish-proxy-container. The operator explicitly requested deployment of the existing fixes to the organization pools. This PR supplies the public build path only; it is not evidence of server deployment.