Repository navigation
fix(frontend): bump next to 16.4.2 and @sentry/nextjs to 10.76.2 - #893
Merged
Merged
Conversation
next < 16.4.1 has two unauthenticated RCE advisories (GHSA-2464-fhr4-w9xw, GHSA-673q-mjm6-r5xr) and @sentry/nextjs < 10.75.2 a middleware bypass via the tunnel route (GHSA-mchm-gjx6-7h55). The Deploy Staging critical Trivy scan of the frontend image fails on them. @next/bundle-analyzer follows next. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BhWKLLcboJNvWt5wzvMbDn
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Deploy Staging failed on main at 29bedee in the frontend image's critical-severity Trivy scan. The frontend runs
next16.3.6 and@sentry/nextjs10.73.0, which have critical advisories:use cachefunctions returning typed arrays (fixed in 16.4.1)Refs #880
Feature Summary
next^16.4.2,@sentry/nextjs^10.76.2,@next/bundle-analyzer^16.4.2npm install;eslint-config-nextandeslint-plugin-react-hooksstay as they are (bumping them turns on new hooks lint rules, which is a separate refactor)Technical Implementation
Dependency-only change. No code, config or env changes.
Test Coverage
./scripts/ci-local.sh frontendpasses: lint, typecheck, build, 293 testsnpm audit --omit=dev(what the runtime image installs): 0 critical, down from 3npm ci --omit=devtree: the next and sentry criticals are gone. The only remaining critical isconcurrent-rubyin@stellar/js-xdr/Gemfile.lock, which Trivy's image mode doesn't scan (the backend image ships the same file and passes) and which is already tracked under Baseline existing dependency findings, then make npm audit, Trivy and cargo audit block PRs (follow-up to #839) #880Checklists
General
./scripts/ci-local.sh frontendand it passes.github/THREAT_MODEL.mdattached (dependency security patch, no change to the threat model)