{"version":"2.1.251","anchor":"plugin-cache-reuse-now-accounts-for-other-running-sessions","canonical_anchor":"plugin-cache-reuse-now-accounts-for-other-running-sessions","heading":"Plugin cache reuse now accounts for other running sessions","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/plugin-cache-reuse-now-accounts-for-other-running-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Plugin cache reuse now accounts for other running sessions\n\nInstalling a plugin no longer yanks a cached copy out from under your other sessions.\n\n**What**\n\nInstalling or linking a plugin now classifies an existing cached copy as in use by another session, safe to reuse as-is, or unclassifiable, and that decides whether the cache is reused or overwritten. An overwrite waits for other sessions to finish rather than pulling the directory out from under them.\n\n**Details**\n\n- Removal logs say `superseded` when a newer version replaced the cache and `incomplete` when the previous write did not finish.\n- Always active for plugin installs; there is no flag.\n\n**Evidence**\n\n`Removing ${qe || Ne ? \"superseded\" : \"incomplete\"} cache directory for ${t} at ${F}`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}