Source Intelligence

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

Stricter owner/repo validation for gh commands

You'll notice
Useful2 Signal0
Bash Tool

Malformed or sneaky owner/repo names are rejected before any gh command is built.

What

Repository references passed to gh commands go through a new validator that checks each path segment against a conservative character class, so malformed or hostile-looking refs are rejected before a command is built.

Details
  • Each segment must match the allowed character class; segments starting with - are rejected outright, as are segments equal to . or ...
  • Applied when parsing both the owner/name and the host/owner/name forms.
  • Active for everyone, no gate.
Evidence

protocol.file.allow=never

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 →