Bbackstage

backstage/v1-47-0-migration-recipe

Backstage 1.47.0: Migration recipe that runs every @backstage v1.47.0 codemod from the registry in a safe order.

backstagemigrationrecipeworkflowupgrade1.47.0
Public
0 executions

Run locally

npx codemod @backstage/v1-47-0-migration-recipe

v1.47.0-migration-recipe

One-shot migration recipe for upgrading a Backstage app to 1.47.0. Chains every @backstage/* v1.47.0 codemod from the Codemod registry through a single workflow so you don't have to run each one by hand.

What it runs

Each step below is a registry package that you can also run on its own. The recipe executes them sequentially in an order aligned with the Backstage 1.47.0 release notes: CSS token renames first, then the structural Table component migration.

#Registry packageWhat it does
1@backstage/rename-bui-css-tokens-v1-47Rename deprecated BUI CSS custom properties (--bui-bg, --bui-bg-tint*) to new equivalents
2@backstage/migrate-table-to-use-table-hookMigrate Table component to new useTable hook API from @backstage/ui

Usage

bash

You can also run the recipe directly from this repo:

bash

AI fixup

The recipe accepts a top-level aiFixup param and forwards it to every step that supports it via the workflow’s args: directive. By default it is false.

bash

You can also run a single codemod with AI fixup independently:

bash

Out of scope (document only)

The following v1.47.0 changes are not covered by codemods and require manual attention:

  • FetchUrlReader constructor now private - use FetchUrlReader.fromConfig instead (narrow internal API)
  • URL reader redirect chain validation - configure reading.allow in app-config.yaml
  • Blueprints moving to @backstage/plugin-app-react - deprecated, not yet removed
  • Color token tint replacements are approximate - the --bui-bg-tint* tokens have "no direct replacement" per changelog; the --bui-bg-neutral-on-surface-0* set is the recommended equivalent

Notes

  • Each step is invoked through the codemod: workflow action and resolved from the Codemod registry, so running the recipe installs the latest published version of every referenced package.
  • The recipe does not reorder edits across codemods; each registry package owns its own before/after behavior. Check the individual READMEs for the details of any single step.
  • Several of the codemods insert TODO(backstage-codemod) markers where a value needs a human review. After the recipe finishes, grep for TODO(backstage-codemod) in your repo to find everything that still needs attention.
  • This recipe is orchestration only - it has no transform script of its own, so there are no fixture tests. Running yarn test in this package validates the workflow schema via codemod workflow validate.

Ready to contribute?

Build your own codemod and share it with the community.