{"version":"2.1.226","anchor":"version-bump-to-2-1-226","canonical_anchor":"version-bump-to-2-1-226","heading":"Version bump to 2.1.226","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.226\/e\/version-bump-to-2-1-226","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.226","markdown":"### Version bump to 2.1.226\n\nThe version number ticks up to 2.1.226; nothing else changes.\n\n**What**\n\nThe build-constant stamp is rewritten: VERSION moves from 2.1.225 to 2.1.226, BUILD_TIME from 2026-08-07T19:37:58Z to 2026-08-08T00:42:40Z, and GIT_SHA to e140b3281c1e8d834468889bd0a5c3fd2f15507c. Nothing changes beyond the reported version.\n\n**Details**\n\n- The constant is inlined at every use site, so all 52 changes in this group are the same object re-stamped.\n- Visible in the startup banner, `--version` output, the `Current version:` line in the update flow, and the update\/downgrade console messages.\n- Sent in the `claude-code\/` and `claude-cli\/` User-Agent strings and in the `x-environment-runner-version` header, where it is prefixed `shr-`.\n- Also drives the daemon-vs-CLI mismatch warning, the \/doctor and feedback reports, the SDK `get_binary_version` control response, the npm update check's `npm view <package>@<tag> version` call, the Datadog sourcemap group identifiers, and the version field on numerous telemetry events.\n- Not gated; everyone on this build sees it.\n\n**Evidence**\n\n`x-environment-runner-version`, `VERSION: \"2.1.226\"`\n\n- Area: Elsewhere\n- Names: `--version`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}