-
Notifications
You must be signed in to change notification settings - Fork 1
[Snyk] Security upgrade babel-loader from 8.4.1 to 10.0.0 #3
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -18,7 +18,7 @@ | |||||
| "@popperjs/core": "^2.11.8", | ||||||
| "@rails/request.js": "^0.0.9", | ||||||
| "@selectize/selectize": "^0.15.2", | ||||||
| "babel-loader": "^8.4.1", | ||||||
| "babel-loader": "^10.0.0", | ||||||
|
||||||
| "babel-loader": "^10.0.0", | |
| "babel-loader": "^8.4.1", |
Copilot
AI
Feb 13, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR description mentions updating yarn.lock, but this project uses pnpm as its package manager (indicated by "packageManager": "pnpm@10.29.3" in package.json). The warning about "Failed to update the yarn.lock" is misleading since this project doesn't use yarn. The actual lock file that needs updating is pnpm-lock.yaml, not yarn.lock. This suggests the automated Snyk PR may have been configured for the wrong package manager.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This version bump is incomplete because
pnpm-lock.yamlstill resolvesbabel-loaderto8.4.1(pnpm-lock.yaml:60-62), so the intended security fix is not actually captured in the lock state. In the CI workflow, dependencies are installed withpnpm install --frozen-lockfile(.github/workflows/rubyonrails.yml:54), which requires the lockfile to matchpackage.json; as committed, this can block installs and leaves the vulnerable dependency pinned until the lockfile is regenerated and committed.Useful? React with 👍 / 👎.