{"version":"2.1.243","anchor":"version-constant-bumped-to-2-1-243","canonical_anchor":"version-constant-bumped-to-2-1-243","heading":"Version constant bumped to 2.1.243","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.243\/e\/version-constant-bumped-to-2-1-243","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.243","markdown":"### Version constant bumped to 2.1.243\n\nThe version number now reads 2.1.243 everywhere it shows up.\n\n**What**\n\nThe build stamp changed from 2.1.242 to 2.1.243. Everything that reports a version now reports the new one, including `--version`, the \/status version row, the updater's npm commands, the user-agent strings and the bug-report Environment Info block.\n\n**Details**\n\n- Only the version, build time and git commit fields changed; the package URL, README URL, issues explainer, feedback channel, hooks worker URL and sourcemap group are untouched.\n- The same build-metadata object is inlined at roughly 118 places, so the daemon start log line, the `x-environment-runner-version` request header and the Remote Control minimum-version message all pick it up together.\n- No behaviour change beyond the reported string.\n\n**Evidence**\n\n`BUILD_TIME: \"2026-08-24T21:05:22Z\"`\n\n- Area: Elsewhere\n- Names: `--version`, `\/status`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}