{"version":"2.1.248","anchor":"cleaning-up-stale-locks-no-longer-removes-the-caller-s-own","canonical_anchor":"cleaning-up-stale-locks-no-longer-removes-the-caller-s-own","heading":"Cleaning up stale locks no longer removes the caller's own","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cleaning-up-stale-locks-no-longer-removes-the-caller-s-own","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cleaning up stale locks no longer removes the caller's own\n\nStale lock cleanup no longer deletes the lock the running process holds.\n\n**What**\n\nThe helper that sweeps away leftover lock files can now be told to spare one path, so a process cleaning up stale siblings does not delete the lock it is currently holding.\n\n**Evidence**\n\n`.filter((o) => o !== t)`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}