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

Git remote URL parsing normalizes leading slashes and percent-encoding

You'll notice
Useful2 Signal0
Git Integration

Git remote URLs differing only by a slash or escaping now resolve to the same repository.

What

Remote URLs that differ only by a leading slash or percent-encoding now resolve to the same repository identity, and malformed paths are rejected rather than half-parsed.

Details
  • The scp-style parser strips leading slashes from the path.
  • The owner/repo result must split into exactly two non-empty segments, otherwise parsing returns null.
  • The URL-form sanitizer attempts decodeURIComponent(r.pathname) inside a try/catch, so a failure to decode leaves the path untouched.
Evidence

r.pathname = decodeURIComponent(r.pathname);

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 →