メニュー
Update Backstage dependencies to the latest version. Use when the user wants to update backstage, upgrade backstage packages, bump backstage version, or keep backstage up to date.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How to build UI in this repo — the bui (@backstage/ui) design system vs legacy @backstage/core-components + MUI v4, which to reach for, and how to read Backstage Storybook component/story source. Use when creating or changing pages, cards, layouts, buttons, or any frontend component.
Patterns for implementing tables. Covers the bui Table ('@backstage/ui') — preferred for new, simple tables — and the feature-rich '@backstage/core-components' Table with search, filtering, and column-visibility persistence.
Common rules for working with this repository
Read, classify, and triage Sentry issues for this Backstage app, propose mitigations, and decide their disposition (fix, resolve, mute, or escalate). Use when given a Sentry issue URL (giantswarm.sentry.io/issues/...), asked to investigate a Sentry error/exception/CSP violation, asked why an image/script/style/font was blocked on a page, or asked to mute/ignore noisy Sentry issues.
Build Backstage backend plugins with createBackendPlugin and core services: DI, httpRouter, secure-by-default auth, Knex DB, routes, testing. Use for APIs and background jobs.
Build Backstage frontend plugins with the new Frontend System: createFrontendPlugin, blueprints, routes, Utility APIs, testing. Use for pages, nav, entity content, or cards.
| name | backstage-update |
| description | Update Backstage dependencies to the latest version. Use when the user wants to update backstage, upgrade backstage packages, bump backstage version, or keep backstage up to date. |
| allowed-tools | Read, Bash, AskUserQuestion |
Update all @backstage packages to the latest release version.
cat backstage.json 2>/dev/null | jq -r '.version'grep -q "plugin-backstage" .yarnrc.yml 2>/dev/null && echo "Yes" || echo "No"Read backstage.json to get the current Backstage release version.
Use AskUserQuestion to ask the user which release channel to use:
Execute the appropriate command based on user selection:
For stable release:
yarn backstage-cli versions:bump
For next release:
yarn backstage-cli versions:bump --release next
After bumping versions, install the new dependencies:
yarn install
Provide the user with resources to check for breaking changes:
Ask the user if they want you to fetch and summarize the changelog for relevant versions.
Run verification commands to ensure no breaking changes:
yarn tsc
If type checking passes, run linting:
yarn lint
Display:
yarn startIf yarn install fails:
yarn dedupe to resolve duplicate packagesIf type checking fails:
If the backstage yarn plugin is not installed:
yarn plugin import https://versions.backstage.io/v1/tags/main/yarn-plugin