{"version":"2.1.220","anchor":"build-stamp-moved-to-2-1-220","canonical_anchor":"build-stamp-moved-to-2-1-220","heading":"Build stamp moved to 2.1.220","tier":"internal","area":"Build Metadata","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.220\/e\/build-stamp-moved-to-2-1-220","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.220","markdown":"### Build stamp moved to 2.1.220\n\nVersion strings in update messages, doctor output and daemon logs were re-stamped to 2.1.220.\n\n**What**\n\nThe inlined build constants appearing in around 40 user-visible and log strings were re-stamped, with no surrounding logic touched.\n\n**Details**\n\n- VERSION 2.1.219 -> 2.1.220, BUILD_TIME 2026-07-24T03:24:19Z -> 2026-07-24T22:17:45Z, GIT_SHA 7006c4c3acac98e554d3997baeda6a7fa4d1ff7c -> 4073f59596e272f39393db4f96abc5f4b10eff21.\n- Affected strings include version output, `claude update` messages, user agents, doctor output and daemon logs.\n\n**Evidence**\n\n`GIT_SHA: \"4073f59596e272f39393db4f96abc5f4b10eff21\"`\n\n- Area: Build Metadata\n- Names: `claude update`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}