chore(upstream-sync): 2026-04-30 pull from router-for-me/CLIProxyAPI#6
Merged
Conversation
- Added `disable-image-generation` configuration flag to disable the `image_generation` tool globally. - Updated payload handling to remove `image_generation` tools from request payload arrays when the flag is enabled. - Modified OpenAI image handlers (`ImagesGenerations`, `ImagesEdits`) to return 404 when the feature is disabled. - Enhanced configuration diff logging to track changes for the `disable-image-generation` flag. - Added accompanying unit tests for the new feature in payload helpers and image handler logic.
leic4u
pushed a commit
that referenced
this pull request
May 1, 2026
…om sync-release-tag Resolves #6. The previous docker-image.yml never produced a published image: 1. It triggered on `push: tags: v*`, but sync-release-tag.yml pushes tags using GITHUB_TOKEN, and GITHUB_TOKEN tag-pushes do NOT cascade to other workflows. 2. The single time it ran (manually, 2026-04-22) it failed — likely missing DOCKERHUB_USERNAME / DOCKERHUB_TOKEN secrets. Changes: docker-image.yml - Single multi-arch job using QEMU + buildx instead of three jobs (amd64 / arm64 / manifest stitching). - Runs on self-hosted `cliproxy` runner (docker host LXC) — no charge, no GitHub-hosted minutes. - Pushes to ghcr.io/${owner}/cli-proxy-api-plus using the built-in GITHUB_TOKEN. No Docker Hub secrets to manage or rotate. - Tags published: :${VERSION}, :latest. Single multi-arch manifest per tag (no -amd64/-arm64 suffix tags or post-build cleanup). - workflow_dispatch accepts an optional `tag` input; the build checks out that ref before building. This is what sync-release-tag.yml invokes. sync-release-tag.yml - After creating (or detecting) a fork tag, explicitly dispatch BOTH release.yaml and docker-image.yml with the tag. Mirrors the existing pattern for release.yaml. Each dispatch is best-effort (`|| true`) so a transient failure in one does not block the other.
leic4u
pushed a commit
that referenced
this pull request
May 1, 2026
Closing #6 yesterday claimed the image was published, but `docker compose up` still 404'd because docker-compose.yml defaulted to `eceasy/cli-proxy-api-plus:latest` — an image that has never existed anywhere (eceasy publishes `cli-proxy-api`, not `-plus`; Plus's old DOCKERHUB_USERNAME workflow never ran successfully). Reported by @simonsmh in #6. Changes: - docker-compose.yml: default image is now ghcr.io/kaitranntt/cli-proxy-api-plus:latest, matching what PR #44 publishes. Users can still override via CLI_PROXY_IMAGE. - .gitattributes: add `docker-compose.yml merge=ours` so the next upstream sync does not silently revert this image path back to upstream's `eceasy/cli-proxy-api:latest`. Image references are the only Plus-specific bit of the compose file; if upstream evolves the rest, we reconcile manually rather than letting auto-merge bring back a broken default. - README.md: add a "Run with Docker" subsection under Getting Started with the GHCR pull commands and a docker-compose snippet, so users can find install instructions without grepping closed issues.
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.
Upstream sync:
router-for-me/CLIProxyAPI→mainCommits being synced:
359ec30d0c5674659d9d73080de378f9a7417c4a..e3e60f914ba82a6caa7a17a717f65a3b2f02285fGate status
go testFAILEDWhat to do
cmd/server/main.go,go.mod,go.sum..gitattributes merge=ours.go build ./... && go test ./....