{"version":"2.1.242","anchor":"plugin-downloads-write-straight-into-the-cache","canonical_anchor":"plugin-downloads-write-straight-into-the-cache","heading":"Plugin downloads write straight into the cache","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/plugin-downloads-write-straight-into-the-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Plugin downloads write straight into the cache\n\nPlugin downloads stream straight into the cache and are hashed on the way in.\n\n**What**\n\nFiles a marketplace plugin pulls down are now streamed directly into the cache and hashed on the way in, instead of first landing in a temporary staging directory. The expected checksum is still verified at the end, and a download that is too large fails rather than filling the cache.\n\n**Details**\n\n- The write refuses to overwrite an existing entry and uses file mode 384 (owner read\/write only) with a size cap.\n- If two sessions fetch the same asset at once, the loser re-checks the digest of what is already there and treats it as a cache hit.\n- Storage failures are reported as `asset_transient` or `asset_too_large`.\n\n**Evidence**\n\n`asset-cache`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}