{"version":"2.1.277","anchor":"plugin-installpublish-path-reworked-with-a-non-strict-cache","canonical_anchor":"plugin-installpublish-path-reworked-with-a-non-strict-cache","heading":"Plugin install can verify declared binary hashes and skip republishing","tier":"notice","area":"Plugin Install","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/plugin-installpublish-path-reworked-with-a-non-strict-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Plugin install can verify declared binary hashes and skip republishing\n\nPlugin installs can now verify a manifest's declared binary hashes and skip re-publishing when they already match\n\n**What**\n\n- The plugin publish\/move logic now returns an explicit \"published\" status, and for plugins without `strictCache`, it takes a faster path that drops the staged clone's `.git` directory and installs directly, bypassing the version-cache rename process used for strictCache plugins.\n\n- When a plugin's manifest declares binaries and a feature check passes, install now passes a `binariesHook` with the declared sha256 hash map into the staging\/publish step, and can report the result as \"kept\" (skipping republish) when the hashes already match.\n\n**Why**\n\nVerifying binary hashes before republishing avoids unnecessary rewrites of unchanged binary files during plugin installs, making installs faster and safer for plugins that ship binaries.\n\n- Area: Plugin Install\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}