{"version":"2.1.232","anchor":"plugin-registry-can-be-read-through-the-storage-backend","canonical_anchor":"plugin-registry-can-be-read-through-the-storage-backend","heading":"Plugin registry can be read through the storage backend","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/plugin-registry-can-be-read-through-the-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Plugin registry can be read through the storage backend\n\nThe installed-plugins file can be loaded through the storage layer, upgrading old registry formats.\n\n**What**\n\nLoading the installed-plugins file gained an asynchronous path that goes through the v5 storage layer rather than reading from disk directly, upgrading old V1 registry files to V2 as it loads.\n\n**Details**\n\n- Results are cached under an epoch counter so a concurrent synchronous load takes precedence.\n- Storage backend failures are mapped to a dedicated registry error, and a defensive error covers a read that completes without an outcome for its key.\n- Nothing in this build shows the new path replacing the existing synchronous load.\n\n**Evidence**\n\n`installed plugins registry read settled without an outcome for its key`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}