From 5f8ee599f5e9832e83ea6bcab791c1258ab683f6 Mon Sep 17 00:00:00 2001 From: Steven Billington Date: Thu, 25 Apr 2024 09:27:40 -0400 Subject: [PATCH] Minor fix on version numbering that I missed earlier in the documentation. Signed-off-by: Steven Billington --- docs/features/software-templates/writing-custom-actions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/software-templates/writing-custom-actions.md b/docs/features/software-templates/writing-custom-actions.md index 96b2540527..fa21c8f7a9 100644 --- a/docs/features/software-templates/writing-custom-actions.md +++ b/docs/features/software-templates/writing-custom-actions.md @@ -142,7 +142,7 @@ argument. It looks like the following: ## Registering Custom Actions -### Register Action With Previous Backend System, Backstage Version < 1.25.x +### Register Action With Previous Backend System, Backstage Version < 1.24.x Once you have your Custom Action ready for usage with the scaffolder, you'll need to pass this into the `scaffolder-backend` `createRouter` function. You @@ -194,7 +194,7 @@ export default async function createPlugin( } ``` -### Register Action With New Backend System, Backstage Version >= 1.25.0 +### Register Action With New Backend System, Backstage Version >= 1.24.0 To register your new custom action in the New Backend System you will need to create a backend module. Here is a very simplified example of how to do that: