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
10 changes: 5 additions & 5 deletions packages/backend-app-api/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,15 @@
"start": "backstage-cli package start"
},
"dependencies": {
"@backstage/backend-common": "workspace:^",
"@backstage/backend-plugin-api": "workspace:^",
"@backstage/backend-common": "0.24.1",
"@backstage/backend-plugin-api": "0.1.0",
"@backstage/backend-tasks": "workspace:^",
"@backstage/cli-common": "workspace:^",
"@backstage/config": "workspace:^",
"@backstage/config-loader": "workspace:^",
"@backstage/config-loader": "0.1.1",
"@backstage/errors": "workspace:^",
"@backstage/plugin-auth-node": "workspace:^",
"@backstage/plugin-permission-node": "workspace:^",
"@backstage/plugin-auth-node": "0.1.0",
Comment on lines 34 to +42
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: Mixing workspace: references and pinned versions for @backstage/* dependencies causes dual-package loading and runtime type errors. Revert pinned versions to workspace:^ to ensure consistent resolution against the local monorepo.

🤖 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/backend-app-api/package.json
Lines: 34-42

Problem: The diff changes five @backstage dependencies from 'workspace:^' to pinned versions (0.24.1, 0.1.0, 0.1.1), while other @backstage dependencies remain as 'workspace:^'. This creates an inconsistent dependency resolution strategy within the monorepo.

Required Action:
1. Determine if this change is intentional (e.g., preparing for external npm publication)
2. If intentional: Update ALL @backstage/* dependencies to use pinned versions for consistency
3. If unintentional: Revert these five dependencies back to 'workspace:^' to maintain monorepo workspace protocol
4. Document the reasoning in commit message or package.json comments

Verify that the chosen strategy aligns with the project's dependency management policy and doesn't break local development or CI/CD pipelines.

"@backstage/plugin-permission-node": "0.1.0",
"@backstage/types": "workspace:^",
"@manypkg/get-packages": "^1.1.3",
"@types/cors": "^2.8.6",
Expand Down
Loading