Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Fetch-output branch parsing requires hex ranges

Under the hood
Useful2 Signal0
Git Integration

Git fetch output is parsed more strictly, so unrelated lines aren't mistaken for updated branches.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.223 →