Claude Code v2.1.223 ·
Fetch-output branch parsing requires hex ranges
Git fetch output is parsed more strictly, so unrelated lines aren't mistaken for updated branches.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Git IntegrationArea: what it touches
Bug FixesKind: in v2.1.223,
Bug FixesSection of the release
What
Parsing of git fetch output is stricter about what counts as an updated ref, reducing false matches on unrelated fetch lines.
Details
- The old..new range must now consist of hex characters rather than any non-whitespace token.
- The
[new branch] alternative is unchanged.
Evidence
[0-9a-f]+\.\.+[0-9a-f]+
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.223 →
