Patch transitive dependency vulnerabilities via overrides#90
Open
exekias wants to merge 1 commit into
Open
Conversation
Clears 3 of 4 Dependabot alerts without downgrading next/drizzle-kit. Leaves the deprecated @esbuild-kit esbuild 0.18 chain (drizzle-kit CLI, dev-only) for an upstream fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Patches three transitive dependency vulnerabilities flagged by Dependabot, using npm
overridesso we keep next 16 and drizzle-kit 0.31 (npm'saudit fix --forcewould downgrade them to next 9 / drizzle-kit 0.18).Fixed (3 of 4 alerts)
postcss 8.4.31undernext8.5.15@babel/core 7.29.07.29.7esbuild 0.28.0undertsx0.28.1Knowingly left for now (1 of 4)
esbuild dev-server request (moderate) via
esbuild 0.18.20under the deprecated@esbuild-kit/core-utils→@esbuild-kit/esm-loaderchain thatdrizzle-kit's CLI still pulls in. Forcing a non-vulnerable esbuild (≥ 0.25) there is a large jump from 0.18 and risks breakingdrizzle-kit. It's a dev/CLI-only path (not shipped, not in the app build), so it's left as accepted risk pending an upstreamdrizzle-kitrelease that drops@esbuild-kit.npm auditdrops from 7 vulnerabilities to 4 (the remaining 4 are that single@esbuild-kitesbuild advisory plus its dependency-chain entries).Verification
All CI steps pass locally with the new lockfile:
tsc --noEmit✓eslint✓npm run lessons:validate✓next build✓🤖 Generated with Claude Code