chore(security): bundle 22 Dependabot fixes for datasheetsChat (npm) - #9
Merged
benfrank241 merged 1 commit intoAug 26, 2026
Conversation
Bump next, postcss (direct) and add scoped overrides for sharp, js-yaml and brace-expansion (1.x and 2.x lines separately). Regenerated with `npm install --package-lock-only`. Closes 22 open Dependabot alerts on datasheetsChat/package-lock.json. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
benfrank241
deleted the
chore/security-daily-20260826-rag-101-workshop-npm-datasheetsChat
branch
August 26, 2026 20:25
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.
Daily security sweep — bundles the Dependabot fixes for
datasheetsChat/package-lock.jsononto a human-authored branch so CI actually runs with repo secrets (Dependabot's own branches don't get them).Closes 22 of the 23 open alerts. One alert has no upstream fix and is backlogged (see below).
Changes
datasheetsChat/package.json+ regeneratedpackage-lock.json(vianpm install --package-lock-only, not a from-scratch regen).Direct bumps (fixed version was already in range):
nextpostcssOverrides (transitive — no direct declaration to bump):
sharp^0.34.3 || ^0.35.3rangejs-yamlbrace-expansion@^1brace-expansion@^2nanoidmoved 3.3.12 → 3.3.18 for free via the postcss bump (no override needed), and next's pinned nestedpostcss@8.4.31deduped away entirely.brace-expansionneeded two version-scoped override keys rather than one global entry: the 1.x and 2.x lines are both present under differentminimatchmajors, so a single global override would have broken one of them.Alerts closed
#42#54#55#56#57#58#59#60#61#62#63#64#65#66#67#69#70#72#74#75#76#77Advisory IDs (22)
npm auditon this branch: 12 vulnerabilities (4 high, 1 moderate, 7 low) → 7 low, all 7 being the un-fixable@ai-sdk/*chain below.Needs a human look
sharp0.34.4 → 0.35.4. A0.xminor is a breaking-change slot in semver, and this pulls in the new@img/sharp-*platform binaries (the only packages added by this PR). It stays inside the rangenext@15.5.24itself declares, and I smoke-tested the native binding locally —sharploads and encodes a PNG against libvips 8.18.6. Still worth a second opinion since it's a native dep.nextstays on 15.5.x.maindoes not currently build — pre-existing, not caused by this PRnpm run buildfails on this branch, and it fails identically on unmodifiedmain. I reproduced it on a clean checkout before touching anything:tsc --noEmitreports the same 8 errors, byte-identical, before and after this change — this PR introduces zero new type errors. The webpack compile stage passes (✓ Compiled successfully); only the typecheck stage fails.The cause is a pre-existing mismatch in
package.jsonthat predates this sweep:ai@^5.0.68is paired with@ai-sdk/openai@^1.1.9/@ai-sdk/react@^1.2.2/@ai-sdk/groq@^1.1.7, andsrc/app/api/chat/route.tsis written against the AI SDK v4 API (parameters:instead ofinputSchema:,toDataStreamResponse()instead oftoUIMessageStreamResponse()). Fixing that is an app-code migration, deliberately not mixed into a security bundle. Tracked separately in the backlog issue.Note that repo CI here is only the GitLeaks secret scan — there is no build/test workflow — so this does not turn CI red.
npm run lintis also not runnable in either tree: no ESLint config is committed, sonext lintdrops into an interactive setup prompt. Unchanged by this PR.Verification performed
npm ci— clean, noERESOLVEnpm run build— compile stage passes; typecheck fails identically tomain(above)tsc --noEmit— diffed againstmain: identical, no new errorssharpnative binding — loads and encodes a PNG (libvips 8.18.6)@img/sharp-*platform set; no unrelated churn🤖 Generated with Claude Code