chore: upgrade @babel/core to ^7.29.6 to address CVE-2026-49356#1333
Conversation
Refreshed the yarn.lock so all transitive @babel/core instances resolve to 7.29.7 (>= 7.29.6), fixing the arbitrary file read via sourceMappingURL comment. Generated with [Linear](https://linear.app/sourcebot/issue/SOU-1357/sourcebot-devsourcebot-cve-2026-49356-babelcore-arbitrary-file-read#agent-session-c9dbdeec) Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
Generated with [Linear](https://linear.app/sourcebot/issue/SOU-1357/sourcebot-devsourcebot-cve-2026-49356-babelcore-arbitrary-file-read#agent-session-c9dbdeec) Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
|
Warning Review limit reached
More reviews will be available in 3 minutes and 58 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
License Audit
Weak Copyleft Packages (informational)
Resolved Packages (20)
|
(#1344) #1333 addressed CVE-2026-49356 but left the @babel/core entry shared by ^7.24.4 and ^7.26.0 (eslint-plugin-react-hooks, react-scan) pinned to 7.29.0, below the patched 7.29.6. Refresh via yarn up -R @babel/core so every transitive instance resolves to 7.29.7. Lockfile-only change. Generated with [Linear](https://linear.app/sourcebot/issue/SOU-1370/sourcebot-devsourcebot-cve-2026-49356-babelcore-arbitrary-file-read#agent-session-a076660e) Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
Fixes SOU-1357
Refreshes
yarn.lockso all transitive@babel/coreinstances resolve to7.29.7(≥ 7.29.6), addressing CVE-2026-49356 (arbitrary file read via a craftedsourceMappingURLcomment).All three instances came in via existing
^7.18.5/^7.24.4/^7.26.0ranges that already admit the patched version, so this is a lockfile-only refresh (yarn up -R @babel/core) with nopackage.jsonchange. Verified withyarn why @babel/core --recursive:@sentry/nextjs → @sentry/bundler-plugin-core → @babel/core@7.29.7eslint-config-next → eslint-plugin-react-hooks → @babel/core@7.29.7react-scan → @babel/core@7.29.7