From c411b5dd1536b79880fbbccf7ce7e6b00bcbf485 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Tue, 11 Feb 2025 12:18:43 +0100 Subject: [PATCH] changesets: update new new changeset with some more information Signed-off-by: Patrik Oldsberg --- .changeset/polite-pumas-joke.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/.changeset/polite-pumas-joke.md b/.changeset/polite-pumas-joke.md index 14d96c3a3a..9b026abc0e 100644 --- a/.changeset/polite-pumas-joke.md +++ b/.changeset/polite-pumas-joke.md @@ -2,4 +2,17 @@ '@backstage/cli': minor --- -Convert backstage-cli new factories into declarative templates +The `new` command is now powered by a new template system that allows you to define your own templates in a declarative way, as well as import existing templates from external sources. See the [CLI templates documentation](https://backstage.io/docs/tooling/cli/templates) for more information. + +The following flags for the `new` command have been deprecated and will be removed in a future release: + +- `--license=`: Configure the global `license` instead. +- `--no-private`: Configure the global `private` instead. +- `--baseVersion=`: Configure the global `version` instead. +- `--npmRegistry=`: Configure the global `publishRegistry` instead. +- `--scope=`: Configure the global `namePrefix` and/or `namePluginInfix` instead. + +As part of this change the template IDs and their options have changed. The following backwards compatibility mappings for the `--select` and `--option` flags are enabled when using the default set of templates, but they will also be removed in the future: + +- `--select=plugin` is mapped to `--select=frontend-plugin` instead. +- `--option=id=` is mapped to `--option=pluginId=` instead.