Skip to content

feat: update to avoid brace-extansion issue #20205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
MaitreGEEK wants to merge 1 commit into from
+1 −1
Closed

feat: update to avoid brace-extansion issue #20205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion packages/node/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@
"@opentelemetry/sdk-trace-base": "^2.6.1",
"@opentelemetry/semantic-conventions": "^1.40.0",
"@prisma/instrumentation": "7.6.0",
"@fastify/otel": "0.18.0",
"@fastify/otel": "0.18.1",
Copy link
Copy Markdown

@cursor cursor bot Apr 10, 2026

Choose a reason for hiding this comment

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

yarn.lock not updated for dependency version bump

High Severity

The package.json bumps @fastify/otel to 0.18.1 (exact pin, no ^/~), but the yarn.lock still resolves @fastify/otel@0.18.0. This inconsistency means yarn install --frozen-lockfile (common in CI) will fail, and the intended security fix for the brace-expansion vulnerability won't actually take effect since the lockfile still pins the old version with the vulnerable transitive dependency. The yarn.lock needs to be regenerated to include the new version.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 53ef9de. Configure here.

"@sentry/core": "10.48.0",
"@sentry/node-core": "10.48.0",
"@sentry/opentelemetry": "10.48.0",
Expand Down
Loading