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.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

Lock release failures now say what went wrong

You'll notice
Useful2 Signal1
Error Messages

Internal lock release failures now show a readable explanation instead of a raw error dump.

What

When Claude Code fails to release an internal lock, it now describes the failure instead of dumping the raw error.

Details
  • A lock that was already released reports that it was no longer held and that the protected section may have run without exclusivity.
  • Any other failure reports that the lock directory could not be removed and is left to go stale.
  • A release that rejects with something that cannot be described is reported as such rather than throwing inside the error handler.
Evidence

lock directory could not be removed and is left to go stale

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.227 →