{"version":"2.1.231","anchor":"build-stamp-bumped-to-2-1-231","canonical_anchor":"build-stamp-bumped-to-2-1-231","heading":"Build stamp bumped to 2.1.231","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.231\/e\/build-stamp-bumped-to-2-1-231","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.231","markdown":"### Build stamp bumped to 2.1.231\n\nThe version number you see is now 2.1.231; nothing else about it changed.\n\n**What**\n\nThe version reported by `claude --version`, the `\/status` Version row, update checks and telemetry is now 2.1.231, up from 2.1.229, with a matching new build time and commit hash. Nothing else changed.\n\n**Details**\n\n- The same version, build timestamp (2026-08-13T07:25:27Z) and commit hash are stamped into roughly 50 places across the bundle, including the `claude-code\/` and `claude-cli\/` user-agent strings, the environment runner version header, the daemon-vs-CLI mismatch warning, the Remote Control minimum-version check, `\/doctor` and updater output, the npm lookup for the latest published version, transcript headers, OpenTelemetry attributes and cache keys.\n- No logic differs anywhere in the group; only the constants.\n\n**Evidence**\n\n`x-environment-runner-version`, `VERSION: \"2.1.231\"`, `GIT_SHA: \"bbff368ec698dbfacfcc9caae5eca91c30f299c3\"`\n\n- Area: Elsewhere\n- Names: `claude --version`, `\/status`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}