2 Commits

Include renames

Author	SHA1	Message	Date
alfadb	3efeba33a4	test(claude): 版本覆盖用例字面量随内置基线升至 2.1.259 ... 这三个用例的字面量 2.1.251 写于内置基线为 2.1.220 的时期，本意是取一个 高于基线的补丁位验证"覆盖不得低于 pin"规则。基线升至 2.1.258 后，2.1.251 落在 pin 之下：IsSupportedCLIVersion 应判 false、resolveCLIVersion 应回落 基线，与用例原意相悖，CI 随之失败。 改为真正高于当前 pin 的最小补丁位 2.1.259，用例语义不变；实现未放宽， constants_cli_version_test.go 中独立的 Fable 5.1 闸门下限 2.1.251 保持不变。	2026-09-07 16:34:35 +08:00
LuckyandClaude Opus 5	e9bad40b10	feat(claude): allow operators to override the advertised CLI version ... Anthropic gates newer models on a minimum Claude Code client version. With CLICurrentVersion pinned at 2.1.220, claude-fable-5-1 fails every request with "Claude Code 2.1.220 does not support this model; version 2.1.251 or newer is required", and the only fix is a release that bumps one constant. Add SUB2API_CLAUDE_CLI_VERSION, mirroring what internal/pkg/xai already does with XAI_GROK_CLI_VERSION. CLICurrentVersion remains the built-in pin; the new CLIVersion() is what every consumer reads. With no env var set the resolved value equals the pin, so existing deployments are unaffected. The value is resolved once at package init rather than per call: the User-Agent header and the request body's cc_version are written by different code paths for the same request, and reading different values would make that request contradict itself. Validation is strict (three numeric segments, not below the pin) because identity_service.go documents what a malformed version does once it reaches an account's persistent fingerprint: sustained 429s without reset headers, 5s fallback cooldown, pool collapse into a 503 storm, and no reset entry point. Invalid values warn and fall back rather than being silently dropped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0168uDMAj9anaJrnH8CeFze6	2026-09-04 18:01:34 +00:00