Version-enforcement settings and update targets are now checked for valid semver before being used
The code that decides whether the current build of Claude Code is blocked from updating now validates the version numbers it's working with. This applies to the update target itself, as well as to the minimumVersion and requiredMaximumVersion organization policy settings (minimumVersion keeps auto-updates from installing anything below a set version; requiredMaximumVersion refuses to start on a version newer than an organization allows). If any of these values isn't a properly formed version number, Claude Code now logs the raw value (truncated) and simply ignores that setting instead of trying to act on bad data.
Previously, a malformed version string in one of these settings could have caused the version-enforcement logic to misbehave in unpredictable ways. Now a bad value is safely ignored and logged, so a typo in an organization's policy configuration won't silently break update or startup behavior.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
* `"version_below_minimum"`: this version of Claude Code is below [`requiredMinimumVersion`](/docs/en/settings-reference#requiredminimumversion) or above [`requiredMaximumVersion`](/docs/en/settings-reference#requiredmaximumversion)monitoring-usage see the edit
Anthropic's documentation has since written up requiredMaximumVersion, on Monitoring.
Fixed update checks erroring every 30 minutes, and claude update hanging when a minimum or maximum version is set, if a proxy returns an…