Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions packages/cli/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -30,15 +30,15 @@
"backstage-cli": "bin/backstage-cli"
},
"dependencies": {
"@backstage/catalog-model": "workspace:^",
"@backstage/catalog-model": "0.1.1",
"@backstage/cli-common": "workspace:^",
"@backstage/cli-node": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/eslint-plugin": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/release-manifests": "workspace:^",
"@backstage/release-manifests": "0.0.1",
Comment on lines +33 to +41
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correctness: Revert these dependencies to workspace:^. Hardcoding versions breaks the monorepo workspace protocol, causing the package to resolve stale versions from the registry instead of the local workspace packages.

🤖 AI Agent Prompt for Cursor/Windsurf

📋 Copy this prompt to your AI coding assistant (Cursor, Windsurf, etc.) to get help fixing this issue

File: packages/cli/package.json
Lines: 33-41

Problem: Three internal Backstage dependencies have been changed from workspace protocol (`workspace:^`) to hardcoded versions (`0.1.1` and `0.0.1`). This breaks the monorepo's dependency management strategy.

Impact: 
- Prevents automatic version synchronization across the workspace
- Creates version drift between packages
- May cause runtime errors if APIs change in newer versions
- Breaks the standard Backstage monorepo workflow

Fix Instructions:
1. Revert `@backstage/catalog-model` from `"0.1.1"` back to `"workspace:^"`
2. Revert `@backstage/config-loader` from `"0.1.1"` back to `"workspace:^"`
3. Revert `@backstage/release-manifests` from `"0.0.1"` back to `"workspace:^"`
4. Ensure all internal `@backstage/*` dependencies use `workspace:^` protocol for proper monorepo version management
5. If specific versions are required for a release, use the workspace's version management tooling instead of hardcoding
✨ Committable Code Suggestion

💡 This is a one-click fix! Click "Commit suggestion" to apply this change directly to your branch.

Suggested change
"@backstage/catalog-model": "0.1.1",
"@backstage/cli-common": "workspace:^",
"@backstage/cli-node": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/eslint-plugin": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/release-manifests": "workspace:^",
"@backstage/release-manifests": "0.0.1",
"bin": {
"backstage-cli": "bin/backstage-cli"
},
"dependencies": {
"@backstage/catalog-model": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/cli-node": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/errors": "workspace:^",
"@backstage/eslint-plugin": "workspace:^",
"@backstage/integration": "workspace:^",
"@backstage/release-manifests": "workspace:^",
"@backstage/types": "workspace:^",
"@esbuild-kit/cjs-loader": "^2.4.1",
"@manypkg/get-packages": "^1.1.3",

"@backstage/types": "workspace:^",
"@esbuild-kit/cjs-loader": "^2.4.1",
"@manypkg/get-packages": "^1.1.3",
Expand Down Expand Up @@ -127,7 +127,7 @@
"style-loader": "^3.3.1",
"sucrase": "^3.20.2",
"swc-loader": "^0.2.3",
"tar": "^6.1.12",
"tar": "^7.5.4",
"terser-webpack-plugin": "^5.1.3",
"util": "^0.12.3",
"webpack": "^5.70.0",
Expand Down
Loading