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.229 Home All releases ←olderv2.1.228 v2.1.231newer→
Claude Code v2.1.229

attribution and includeCoAuthoredBy no longer raise settings-conflict warnings

You'll notice
Useful3 Signal1
Settings

Setting commit attribution in more than one place no longer triggers a conflict warning.

attributionincludeCoAuthoredBy
What

These two settings are now excluded from the check that warns when a managed or inline setting conflicts with your own, so setting commit attribution in more than one place stops producing a warning.

Details
  • The attribution settings object now accepts extra keys rather than rejecting them.
  • New helpers derive the commit trailer state from that object as explicitly enabled, implicitly enabled, or disabled.
Evidence

e !== "attribution" && e !== "includeCoAuthoredBy"

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