update wording

Signed-off-by: Peter Macdonald <peterm4c@pm.me>
2026-03-31 13:30:00 +02:00
parent a3c65c8e2a
commit 4a1b7f228d
2 changed files with 3 additions and 1 deletions
@@ -9,7 +9,7 @@ This skill helps fully migrate an existing Backstage plugin from the old fronten

 This is the preferred approach for internal plugins that are only used in a single app, since there is no need to maintain backward compatibility. It can also be used for published plugins when you're ready to drop old system support entirely.

-It is highly recommended to be on Backstage version 1.49.x or above. This can be verified by looking in the `backstage.json` file in the root of the repository.
+It is highly recommended to be on Backstage version 1.49.x or above before starting this, although not mandatory, you may face issues with some of the instructions below. This can be verified by looking in the `backstage.json` file in the root of the repository.

 ## Key Differences from Dual Support

@@ -9,6 +9,8 @@ This skill helps add new frontend system (NFS) support to an existing Backstage

 This is the preferred approach for published plugins or plugins that are used by external parties, since it avoids forcing consumers to migrate their app before they are ready.

+It is highly recommended to be on Backstage version 1.49.x or above before starting this, although not mandatory, you may face issues with some of the instructions below. This can be verified by looking in the `backstage.json` file in the root of the repository.
+
 ## Key Concepts

 - **Dual entry point:** The plugin keeps its existing `src/plugin.ts` (old system) and adds a new `src/alpha.tsx` (new system)