{"version":"2.1.232","anchor":"plugin-and-marketplace-state-saved-through-atomic-updates","canonical_anchor":"plugin-and-marketplace-state-saved-through-atomic-updates","heading":"Plugin and marketplace state saved through atomic updates","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/plugin-and-marketplace-state-saved-through-atomic-updates","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Plugin and marketplace state saved through atomic updates\n\nRefreshing a marketplace writes its record in one transaction instead of rewriting the whole file.\n\n**What**\n\nRefreshing a marketplace now updates its record inside a single transactional write that stamps the last-updated time, instead of mutating memory and rewriting the whole file.\n\n**Details**\n\n- The installed-plugins save error now wraps its underlying cause rather than passing it through bare.\n- The plugin catalog fetch moved from an ad-hoc promise latch to a shared loader.\n- Plugin startup awaits a migration step when a storage handle is supplied.\n\n**Evidence**\n\n`lastUpdated`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}