Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Old-version cleanup now skips itself when it cannot check which versions are in use

Claude Code checks its lock folder before deleting old installed versions and skips cleanup entirely if it cannot read it

You'll notice Bug Fixes
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Auto-UpdaterArea: what it touches
Bug FixesKind: in v2.1.318,
Bug FixesSection of the release

Unclear It is not clear on which operating systems the per-process lock is written.

What

Claude Code deletes old versions of itself from your computer from time to time. Before it does, it now reads the folder of lock files. A lock file is a small marker a running copy of Claude Code leaves to say a version is in use. If that folder cannot be read, Claude Code skips the cleanup and logs "Skipping version cleanup: could not read the locks, so lock protection is unavailable". Previously each version was checked one at a time.

Each running copy of Claude Code can also now write a lock tied to its own process ID, the number your operating system gives a running program.

Why

This stops Claude Code from deleting a version that another open copy of Claude Code is still running.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear on which operating systems the per-process lock is written.

See this entry in the whole of v2.1.318 →

Feedback