{"version":"2.1.238","anchor":"plugin-binaries-are-cached-by-content-hash-and-retried-on-fa","canonical_anchor":"plugin-binaries-are-cached-by-content-hash-and-retried-on-fa","heading":"Plugin binaries are cached by content hash and retried on failure","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/plugin-binaries-are-cached-by-content-hash-and-retried-on-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Plugin binaries are cached by content hash and retried on failure\n\nPlugin binaries are cached and verified by hash, and flaky downloads retry automatically.\n\n**What**\n\nDownloaded plugin binaries now land in a cache entry named by their sha256 and verified against it, staged in a temporary directory first and written with restrictive permissions, then swept on a time-to-live. Transient download failures retry on a backoff schedule bounded by a deadline.\n\n**Details**\n\n- Staging directories are prefixed `.binary-staging-`.\n- The hashed-storage path is conditional; a direct filesystem fallback is retained.\n- Storage failures are wrapped in a distinctly named error rather than surfacing raw.\n\n**Evidence**\n\n`.binary-staging-`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}