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

Claude Code v2.1.242 ·

Workload identity token refresh can proceed without the cross-process lock

Workload identity token refresh can now go ahead without the cross-process lock rather than failing.

Under the hood Improvements
JSON All of v2.1.242
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.242,
ImprovementsSection of the release
What

The lock that serializes OAuth refreshes for workload identity federation now has two modes. Fail-closed retries acquisition 5 times; fail-open retries 15 and, if it still cannot get the lock, refreshes anyway without cross-process serialization rather than failing the refresh.

Details
  • The fail-open path logs a debug line explaining that it proceeded unlocked.
  • The existing lock acquire and release telemetry now records which mode was in use.
  • The mode is chosen per call site, not by a user setting.
  • Workload identity client state (the credentials promise, token cache, resolved base URL and failed access tokens) moved from module globals into a resettable object.
Evidence

wif: credentials lock unavailable at

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →

Feedback