From fe72a38768bc21a5fc9eb8eb36eaec1dba2f8239 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Tue, 19 May 2026 11:16:14 +0200 Subject: [PATCH] Mark renderInTestApp nav removal as breaking in changeset Bump frontend-test-utils as minor with user-facing impact guidance. Signed-off-by: Patrik Oldsberg Co-authored-by: Cursor --- .changeset/remove-nav-item-blueprint-test-utils.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/.changeset/remove-nav-item-blueprint-test-utils.md b/.changeset/remove-nav-item-blueprint-test-utils.md index ef553119b5..b480688b07 100644 --- a/.changeset/remove-nav-item-blueprint-test-utils.md +++ b/.changeset/remove-nav-item-blueprint-test-utils.md @@ -1,5 +1,9 @@ --- -'@backstage/frontend-test-utils': patch +'@backstage/frontend-test-utils': minor --- -Disabled the app nav extension in `renderInTestApp`, removing the legacy nav-item rendering stub. +**BREAKING**: `renderInTestApp` no longer renders a sidebar or legacy `nav-item` extensions. The app nav extension is now disabled in the minimal test app shell, along with the layout and routes extensions. + +If your tests passed `features` containing `nav-item` extensions and asserted on links or labels in that stub sidebar, switch to `renderTestApp` instead — it uses the real app shell and discovers nav items from page extensions. + +If you only use `renderInTestApp` to mount a component with APIs or route refs, there is no change.