From 4114d4b95598a63af079f7bbb720eda805413289 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Tue, 14 Apr 2026 14:39:44 +0200 Subject: [PATCH] Clarify that ModelProcessor has no effect on default catalog usage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Opus 4.6 (1M context) Signed-off-by: Fredrik Adelöw --- .changeset/catalog-backend-model-processor.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.changeset/catalog-backend-model-processor.md b/.changeset/catalog-backend-model-processor.md index f32bb6e261..eb461dc3ef 100644 --- a/.changeset/catalog-backend-model-processor.md +++ b/.changeset/catalog-backend-model-processor.md @@ -2,4 +2,4 @@ '@backstage/plugin-catalog-backend': minor --- -Added `ModelProcessor` that validates catalog entities against the compiled catalog model schemas, and integrated it into the `CatalogBuilder` and `CatalogPlugin`. +Added `ModelProcessor` that validates catalog entities against the compiled catalog model schemas, and integrated it into the `CatalogBuilder` and `CatalogPlugin`. This processor is only activated if you explicitly add catalog model sources to your backend; there is no functional change for regular catalog usage.