Fix template name collision between new and legacy frontend plugin templates

The legacy frontend plugin template had the same name (`frontend-plugin`) as
the new frontend plugin template, causing a conflict error when both were shown
(e.g. when the frontend system could not be auto-detected). Rename the legacy
template to `frontend-plugin-legacy` so both can coexist.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Vincenzo Scamporlino <vincenzos@spotify.com>
This commit is contained in:
Vincenzo Scamporlino
2026-03-30 23:22:03 +02:00
parent feaf3d1ade
commit e38bcefb99
4 changed files with 14 additions and 26 deletions
+1 -1
View File
@@ -2,4 +2,4 @@
'@backstage/cli-module-new': patch
---
Rename the legacy `frontend-plugin` to `legacy-frontend-plugin`
Rename the legacy `frontend-plugin` to `frontend-plugin-legacy`