Releases: HeyJiqingCode/CopilotGateway
Releases · HeyJiqingCode/CopilotGateway
Release list
v1.0.0
CopilotGateway v1.0.0
First independent release. Originally forked from whtsky/copilot2api (diverged after upstream v0.3.1); the notes below cover this fork's own changes only.
Highlights
- Web Dashboard — login-protected model catalog at
/: latest generation of each model series, per-model details (limits, capabilities, pricing), one-click copy of the endpoint URL and gateway API keys, bilingual UI (English / 中文) with remembered language preference. Enabled only whenCOPILOTGW_WEB_USERNAME/COPILOTGW_WEB_PASSWORDare set. - API key auth — a key is required for every request (
Authorization: Bearerorx-api-key), with comma-separated multi-key support; safe to deploy beyond localhost. - Release automation — multi-arch Docker images on GHCR (
x.y.z/vx.y.z/latest, published on version tags only) and cross-platform binaries (linux/darwin/windows × amd64/arm64) via GoReleaser.
Breaking Changes
- Environment variable prefix renamed:
COPILOT2API_*→COPILOTGW_* - Default credentials directory moved to
~/.config/copilotgateway x-goog-api-keyheader and?key=query-string auth removed (Gemini endpoints no longer exist)- Cross-format request routing removed — each endpoint forwards as-is to the API it natively speaks (OpenAI →
/chat/completions&/responses, Anthropic →/v1/messages) /v1/embeddings,/usage, Gemini/v1beta/*, and AmpCode routes removed- Go module renamed to
github.com/HeyJiqingCode/CopilotGateway
Features & Fixes
- Configurable spoofed client headers (
COPILOTGW_EDITOR_VERSION,COPILOTGW_PLUGIN_VERSION,COPILOTGW_CHAT_USER_AGENT,COPILOTGW_API_VERSION) - Expose long-context model metadata via VS Code-style catalog headers
- Strip reasoning fields for models that do not support reasoning effort
- Clear revoked GitHub credentials automatically and re-run device flow
- Unauthenticated
/healthendpoint for load balancer probes - Shared 5-minute models cache backing both
/v1/modelsand capability lookups
Deployment Notes
Upgrading from a copilot2api-era deployment requires renaming the COPILOT2API_* env vars to COPILOTGW_* and pointing the credentials volume at /root/.config/copilotgateway.