{"version":"2.1.236","anchor":"plugin-cache-writes-can-route-through-a-new-storage-backend","canonical_anchor":"plugin-cache-writes-can-route-through-a-new-storage-backend","heading":"Plugin cache writes can route through a new storage backend","tier":"soon","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/plugin-cache-writes-can-route-through-a-new-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Plugin cache writes can route through a new storage backend\n\nPlugin cache file operations can go through a new storage layer, off unless a remote setting enables it.\n\n**What**\n\nPublishing, adopting, probing and clearing plugin cache folders can go through a storage interface instead of direct file calls, falling back to ordinary file operations on invalid-argument, not-a-directory and cross-device errors. It is off unless a remote setting turns it on, and the decision is fixed once per process.\n\n**Details**\n\n- Publishing is refused when the cache path is reached through a symlink.\n- Stray orphan markers and set-aside replaced versions are cleaned up.\n- Session transcript appends, saved tool results and stored shell output use the same path.\n\n**Evidence**\n\n`refused to publish a staged plugin through a symlinked cache folder (v5 backend)`\n\n- Area: Plugins\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}