Upgrading Backstage with versions:bump and the Upgrade Helper
A repeatable monthly upgrade: running versions:bump, reading changesets, applying template changes from the Upgrade Helper to your app and backend packages, and testing before release.
Backstage upgrades
Specific Backstage upgrade jobs beyond routine releases: bumping versions, Node.js changes, catching up old apps, custom plugin compatibility, search engine changes and plugins that moved repositories.
Upgrading Node.js for Backstage
Moving a Backstage app to a newly supported Node.js release: the two-version support window, matching Docker base images and CI, native modules and when Backstage drops the older release.
Catching up a Backstage app that is many releases behind
Bringing an app that has skipped a year or more of releases up to date: stepping through versions, handling deprecations, new backend and frontend system changes along the way, and when rebuilding the app is cheaper.
Keeping custom Backstage plugins compatible across upgrades
Maintaining internal plugins as core APIs change: deprecated packages such as backend-common, extension points, testing plugins against new releases, and owning the upgrade work.
Upgrading Backstage search from Elasticsearch 7 to 8
Elasticsearch 7 is no longer supported by Backstage search: moving to Elasticsearch 8.19 or later or to OpenSearch, reindexing, and the Postgres engine as a simpler option.
Updating plugins that moved to the Backstage community-plugins repository
Switching dependencies for plugins that left the core repository: new package names and release cadence, checking maintenance status, and pinning versions that match your Backstage release.
