Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.229entry #105

Claude Code v2.1.229 ·

attribution and includeCoAuthoredBy no longer raise settings-conflict warnings

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

You'll notice Improvements
JSON All of v2.1.229
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SettingsArea: what it touches
ImprovementsKind: in v2.1.229,
ImprovementsSection of the release
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.

Read from
Names in the bundleattributionincludeCoAuthoredBy

See this entry in the whole of v2.1.229 →

Feedback