Merge branch 'main' into next

demo/site/cache-handler.ts

@@ -164,4 +164,9 @@ export default class CacheHandler {
         }
         fallbackCache.set(key, value, { size: stringData.length });
     }
+
+    async revalidateTag(tags: string | string[]): Promise<void> {
+        if (tags.length === 0) return;
+        console.warn("CacheHandler.revalidateTag", tags);
+    }
 }

docs/docs/2-core-concepts/7-dependencies/index.md

@@ -65,6 +65,34 @@ You must recreate the block index views after
 You can automate this process by following the steps in the [migration guide](/docs/migration-guide/migration-from-v5-to-v6/#block-index).
 For new projects, it should already be automated.
 
+### Providing dependency information
+
+If your block depends on certain entities, you should provide dependency information.
+You can do that using the `indexData()` method in your block data class like this:
+
+```ts
+class MyCustomBlockData extends BlockData {
+    // ...
+
+    indexData(): BlockIndexData {
+        if (this.damFileId === undefined) {
+            return {};
+        }
+
+        return {
+            dependencies: [
+                {
+                    targetEntityName: DamFile.name,
+                    id: this.damFileId,
+                },
+            ],
+        };
+    }
+}
+```
+
+This works for all entities - not just `DamFile`.
+
 ### Displaying dependencies in the admin interface
 
 Next, you probably want to display the dependencies or dependents (usages) of an entity in the admin interface.