From 55b2ef613833437c329b0f1605c82b4d35c01365 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Thu, 29 Jan 2026 13:58:21 +0100 Subject: [PATCH] Add changesets for API conflict error behavior Added changesets documenting that API factory conflicts are now treated as errors that block app startup, reverting the previous warning behavior. Signed-off-by: Patrik Oldsberg Signed-off-by: Patrik Oldsberg --- .changeset/api-override-conflict-error-defaults.md | 5 +++++ .changeset/api-override-conflict-error.md | 5 +++++ 2 files changed, 10 insertions(+) create mode 100644 .changeset/api-override-conflict-error-defaults.md create mode 100644 .changeset/api-override-conflict-error.md diff --git a/.changeset/api-override-conflict-error-defaults.md b/.changeset/api-override-conflict-error-defaults.md new file mode 100644 index 0000000000..703f76fb6e --- /dev/null +++ b/.changeset/api-override-conflict-error-defaults.md @@ -0,0 +1,5 @@ +--- +'@backstage/frontend-defaults': minor +--- + +**BREAKING**: The `API_FACTORY_CONFLICT` warning is now treated as an error and will prevent the app from starting. diff --git a/.changeset/api-override-conflict-error.md b/.changeset/api-override-conflict-error.md new file mode 100644 index 0000000000..ed88452ccf --- /dev/null +++ b/.changeset/api-override-conflict-error.md @@ -0,0 +1,5 @@ +--- +'@backstage/frontend-app-api': minor +--- + +**BREAKING**: Updated the behavior of the new API override logic to reject the override and block app startup instead of just logging a deprecation warning.