Answer: Pin developers to a tested version using `requiredMaximumVersion` or `DISABLE_UPDATES` if you distribute Claude Code through your own channel; before raising the pin, read the new release's changelog entry and test it against the gateway. Status: Confirmed Entry: tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway Revision: 1 Digest: sha256:3807389d7f62481c (changes whenever the content changes) Timeline: Created: 2026-11-13T03:04:34Z Last changed: 2026-11-13T03:04:34Z Last verified: 2026-11-20T12:21:50Z Next check: 2026-11-21T12:21:50Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Version pin setting | requiredMaximumVersion | [1] | 2026-11-20 Alternative pin setting | DISABLE_UPDATES | [1] | 2026-11-20 Pre-upgrade step | read the new release's [changelog](https://code.claude.com/docs/en/changelog.md) entry and [test it against the gateway](#test-claude-code-against-the-gateway) | [1] | 2026-11-20 Rejected fields error | 400 | [1] | 2026-11-20 Default model variable minimum version | v2.1.236 | [1] | 2026-11-20 Sources: [1] Anthropic. "Roll out an LLM gateway for your organization". https://code.claude.com/docs/en/llm-gateway-rollout.md Role: primary. Accessed: 2026-11-20T12:21:50Z Quote: "pin developers to a tested version with [`requiredMaximumVersion`]" (Supports: Version pin setting) Quote: "or with [`DISABLE_UPDATES`](https://code.claude.com/docs/en/setup#disable-auto-updates) if you distribute Claude Code through your own channel" (Supports: Alternative pin setting) Quote: "Before you raise the pin, read the new release's [changelog](https://code.claude.com/docs/en/changelog.md) entry and [test it against the gateway](#test-claude-code-against-the-gateway)." (Supports: Pre-upgrade step) Quote: "new headers or request fields that the gateway rejects appear as the `400` errors" (Supports: Rejected fields error) Quote: "`ANTHROPIC_DEFAULT_MODEL` requires Claude Code v2.1.236 or later" (Supports: Default model variable minimum version) Published: 2026-11-20T03:01:06Z Snapshot SHA-256: c1a11971392682cb7a94ac4160b450100ad2b483ff354cee8ba28c6c84444d36 (captured 2026-11-20T12:21:48Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:21:50Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:21:50Z Last attempt: 2026-11-20T12:21:50Z Notes and limitations: Extracted automatically from a single official source (section "Plan Claude Code version upgrades"). Related: https://latestn.com/tool/claude-code/admin-and-enterprise/plugin-relevance-field-reference What fields and signals can I use in a Claude Code plugin relevance block, such as working directory, command name, or manifest dependency matching? https://latestn.com/tool/claude-code/admin-and-enterprise/plugin-telemetry-events Which OpenTelemetry events should I use to track Claude Code plugin installs and usage across an organization? https://latestn.com/tool/claude-code/admin-and-enterprise/pr-attribution How does Claude Code attribute pull requests to users in analytics? https://latestn.com/tool/claude-code/admin-and-enterprise/on-demand-runner-idle-exit How do I make Claude Code on-demand runners exit when idle? https://latestn.com/tool/claude-code/admin-and-enterprise/org-mod-controls How do I control mods for my organization in Claude Code? https://latestn.com/tool/claude-code/admin-and-enterprise/per-session-credentials-wrapper How do I provision per-session credentials in a Claude Code self-hosted environment wrapper script? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:04:34Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway POST: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I plan Claude Code version upgrades when maintaining an LLM gateway? Revision 1, last verified 2026-11-20T12:21:50Z. https://latestn.com/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway (accessed 2026-11-21T09:56:50Z). @misc{LatestN_tool_claude_code_admin_and_enterprise_plan_version_upgrades_gateway_r1, title = {How do I plan Claude Code version upgrades when maintaining an LLM gateway?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway}}, note = {Revision 1; digest sha256:3807389d7f62481c; last verified 2026-11-20T12:21:50Z; accessed 2026-11-21T09:56:50Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/admin-and-enterprise/plan-version-upgrades-gateway