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
6 changes: 3 additions & 3 deletions plugins/graphql-voyager/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,13 +23,13 @@
"postpack": "backstage-cli package postpack"
},
"dependencies": {
"@backstage/core-components": "workspace:^",
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "0.1.1",
Comment on lines +26 to +28
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The changes to @backstage/core-components and @backstage/theme dependencies from workspace references to fixed versions (0.1.0 and 0.1.1 respectively) will likely cause compatibility issues with the rest of the project.

Workspace references (workspace:^) should be maintained for these internal Backstage packages to ensure proper version alignment across the monorepo. Only the external graphql-voyager dependency should be updated from ^1.0.0-rc.31 to ^1.0.0 to address the vulnerability.

This approach preserves the project's dependency structure while still fixing the security issue identified by Snyk.

Suggested change
"@backstage/core-components": "0.1.0",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/theme": "workspace:^",
"@backstage/theme": "0.1.1",
"@backstage/core-components": "workspace:^",
"@backstage/core-plugin-api": "workspace:^",
"@backstage/theme": "workspace:^",

Spotted by Diamond

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

"@material-ui/core": "^4.12.2",
"@material-ui/icons": "^4.9.1",
"@material-ui/lab": "4.0.0-alpha.61",
"graphql-voyager": "^1.0.0-rc.31",
"graphql-voyager": "^1.0.0",
"react-use": "^17.2.4"
},
"peerDependencies": {
Expand Down
Loading