chore(deps): group low-risk frontend bumps (ai, eslint, vite, types) - #229
Merged
Conversation
Batches the eight low-tier bun dependabot PRs into one change. Caret ranges are restored after `bun add` writes exact pins, so only the version floors move in package.json. - ai 7.0.62 -> 7.0.68 (supersedes #208) - @ai-sdk/react 4.0.65 -> 4.0.71 (supersedes #214) - globals 17.8.0 -> 17.10.0 (supersedes #211) - eslint 10.8.0 -> 10.8.1 (supersedes #212) - @vitejs/plugin-react 6.0.4 -> 6.0.5 (supersedes #215) - eslint-plugin-react-refresh 0.5.3 -> 0.5.4 (supersedes #216) - @types/node 26.1.2 -> 26.2.0 (supersedes #217) - vite 8.2.0 -> 8.2.1 (supersedes #218) Verified against the origin/main baseline: build 0 errors (same), lint 0 errors (same), audit 5 -> 4 vulnerabilities. eslint, eslint-plugin-react-refresh and vite produce those counts, so the findings were diffed rather than the counts alone: eslint output is byte-identical, and the build output differs only in the vite version banner. The dropped advisory is GHSA-2v37-7h3g-55p8 (nanoid, high) - vite 8.2.1 pulls postcss 8.5.26, which requires nanoid >=3.3.18. Thirteen lock entries moved: the eight above plus five internals each parented by one of them (@ai-sdk/gateway via ai, @ai-sdk/mcp via @ai-sdk/react, jiti via eslint and vite, postcss and nanoid via vite). All five are past the 14-day cooldown, as are the eight direct bumps. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011wzZeis7evtxWQtZaQWis6
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 was referenced Sep 3, 2026
westonplatter
pushed a commit
that referenced
this pull request
Sep 3, 2026
Resolves the conflict #229 created: both branches moved adjacent lines in frontend/package.json and re-resolved frontend/bun.lock from the same base. Resolution keeps both sides - typescript-eslint ^8.67.0 from this branch, vite ^8.2.1 and the other seven bumps from main. The lock was regenerated with `bun install` rather than hand-merged; it now differs from main by exactly the 11 typescript-eslint entries this PR is for. Re-verified against the new origin/main baseline (which now carries #229): build 0 errors (same), lint 0 errors (same), audit 4 vulnerabilities (same - the nanoid advisory #229 dropped stays dropped). eslint output is byte-identical, typecheck clean, bun test 71 pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011wzZeis7evtxWQtZaQWis6
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.
Summary
Batches the eight open low-tier bun dependabot PRs into one reviewable change, and picks up a high-severity transitive advisory along the way.
bun addwrites exact pins and discards the caret, so the ranges were restored afterwards —package.jsonmoves only the eight version floors, nothing changed dep/devDep sections.ai@ai-sdk/reactglobalseslint@vitejs/plugin-reacteslint-plugin-react-refresh@types/nodeviteFeatures
N/A
Refactoring
N/A
Fixes
nanoid, high — custom generators loop indefinitely when size is zero). No bot PR could reach it:nanoidhas no direct entry and sits undervite › postcss.vite8.2.1 pullspostcss8.5.26, which requiresnanoid >=3.3.18, so the advisory resolves without anoverridesentry. Audit goes 5 → 4.Verification
Measured with
compare_baseline.py --adapter bun, which diffs a detached worktree atorigin/mainagainst this tree:tsc -b+vite build)eslint .)bun audit)Three of the eight (
eslint,eslint-plugin-react-refresh,vite) are in the adapter'sbaseline_tools— they produce the counts above, so an unchanged number is not by itself evidence. The findings were diffed directly:bun run lintoutput is byte-identical before and after.bun run buildoutput differs only in thevite v8.2.0→v8.2.1banner; the emitted asset list and hashes are unchanged.Also run locally, matching the CI
frontendjob:bun run typecheck(clean) andbun test(71 pass, 0 fail).Lock blast radius: 13 entries moved for 8 requested packages. The 5 extras are each parented by one of the eight, not a graph re-resolve —
@ai-sdk/gateway4.0.54 viaai,@ai-sdk/mcp2.0.33 via@ai-sdk/react,jiti2.7.0 viaeslint/vite,postcss8.5.26 andnanoid3.3.18 viavite.Cooldown: all thirteen versions — the eight direct bumps and the five transitive extras that no bot PR ever proposed — are past the repo's 14-day window (oldest 15d,
aiand@ai-sdk/*;bunfig.tomlminimumReleaseAgeenforces this mechanically on the direct installs).Documentation
None needed — no behavior change.
Additional notes
typescript-eslint8.66.0 → 8.67.0) is medium tier and ships separately, so a lint regression from the tool that produces the lint count stays bisectable.@babel/core,@humanfs/node,browserslist×2) and needoverrides— out of scope here, since the skill ships pins as their own PR.grouped-dependency-upgradesskill.🤖 Generated with Claude Code
https://claude.ai/code/session_011wzZeis7evtxWQtZaQWis6
Generated by Claude Code