{"version":"2.1.224","anchor":"cached-data-moves-to-a-keyed-storage-backend","canonical_anchor":"cached-data-moves-to-a-keyed-storage-backend","heading":"Cached data moves to a keyed storage backend","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/cached-data-moves-to-a-keyed-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Cached data moves to a keyed storage backend\n\nChangelog, model and issue caches now read from a keyed storage backend when one exists.\n\n**What**\n\nCaches for the closed-issues list, model capabilities, gateway models and the changelog now look themselves up by a namespaced key and read from a storage backend when one is available, falling back to the previous plain-file reader when it is not.\n\n**Details**\n\n- Whether the backend path or the file path runs is decided by whether a backend is present at runtime.\n- Failures coming from the backend are now reported distinctly from unexpected errors.\n\n**Evidence**\n\n`closed-issues cache read failed (v5 backend error)`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}