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
4 changes: 2 additions & 2 deletions packages/cli/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"@backstage/cli-common": "workspace:^",
"@backstage/cli-node": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Replacing a workspace dependency with a fixed version ("@backstage/config-loader": "0.1.1") breaks the monorepo's linked development pattern. In a monorepo, workspace dependencies ensure that packages use each other's latest code during development.

This change could:

  1. Prevent local changes in config-loader from being reflected in the CLI
  2. Create version conflicts with other packages that expect the workspace version
  3. Make development and testing more difficult

Consider either:

  • Keeping the workspace dependency ("workspace:^")
  • Using a version range that includes the current workspace version
  • Documenting why this specific fixed version is required
Suggested change
"@backstage/config-loader": "0.1.1",
"@backstage/config-loader": "workspace:^",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

"@backstage/errors": "workspace:^",
"@backstage/eslint-plugin": "workspace:^",
"@backstage/integration": "workspace:^",
Expand Down Expand Up @@ -131,7 +131,7 @@
"terser-webpack-plugin": "^5.1.3",
"util": "^0.12.3",
"webpack": "^5.70.0",
"webpack-dev-server": "^4.7.3",
"webpack-dev-server": "^5.2.2",
"webpack-node-externals": "^3.0.0",
"yaml": "^2.0.0",
"yml-loader": "^2.1.0",
Expand Down
Loading