Adjust versioning scheme and introduce selective auto-update setting

Description

Currently the versioning of Claude Code only increments patch numbers according to semantic versioning (e.g., 1.0.105), while the minor version number remains unused. Since new versions are released almost daily, it becomes difficult to distinguish between true patch releases and more substantial updates. Recently, issues such as permission and settings bugs required rollbacks or stopping auto-updates completely.

Problems

• All updates are pushed as patch versions, even if they include non-trivial changes.
• Hard to differentiate between small fixes and larger functional changes.
• The only option to avoid updates is to disable them entirely with DISABLE_AUTOUPDATER.

Proposed Solution

1. Adopt proper semantic versioning practices:

• Use minor versions for new features, configuration changes, or updates that may affect workflows.
• Reserve patch versions for minimal changes, fixes, or security patches.

1. Introduce a configurable update setting:

• In addition to DISABLE_AUTOUPDATER, provide a setting that allows choosing update behavior:
• Accept only patch updates.
• Accept patch and minor updates.

Benefits

• Clearer differentiation between types of releases.
• Gives (enterprise) developers the ability to stay on a stable, well-tested minor version until a new minor release is available, without being exposed to potential instability from daily patch-level pushes.
• Reduced risk of issues caused by unintended auto-updates.