Repository navigation
chore: bump lucide-react to 1.34.0 and @types/node to 26.3.0 - #12
Merged
Merged
Conversation
Both are same-major updates that the existing caret ranges already allowed; the declared ranges are bumped to match what is installed. Lockfile churn beyond the two packages is limited to peer-key rewrites where the @types/node version appears inside other packages' resolution hashes (next, vite, vitest, sharp, @vercel/analytics). Nothing else re-resolved. Verified: pnpm dedupe --check clean (single @codemirror/state@6.7.1), pnpm check green (545 unit tests), pnpm test:e2e green (25 passed). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C5zaYdMzMZAVhvuLWQqKWB
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Routine dependency bump from a dependency audit. Two packages, both same-major, both already permitted by the existing caret ranges.
lucide-react@types/nodeThe declared ranges are bumped to
^1.34.0/^26.3.0so the manifest matches what is actually installed.Diff scope
Two lines in
package.json. The 27 changed lines inpnpm-lock.yamlare all peer-key rewrites —@types/node's version string appears inside the resolution hashes ofnext,vite,vitest,sharp, and@vercel/analytics. No other package re-resolved to a different version.Verification
pnpm dedupe --check— clean, lockfile unchanged.@codemirror/statestill resolves to a single6.7.1; a duplicate there has broken the production editor after a past lockfile refresh, so it is checked explicitly.pnpm check— green. Biome + ESLint +tsc --noEmit+ Vitest (545 tests across 14 files). The 48 ESLint warnings are pre-existing a11y / react-hooks noise, unchanged by this PR.pnpm test:e2e— 25 passed, 2 skipped, including the CSP specs and the "JSON never leaves the browser" privacy spec.Not included
nextand@next/eslint-plugin-nextare both one patch behind (16.3.2 → 16.3.3), but they are pinned exactly rather than with carets, which reads as deliberate. Bumping them needs a manifest edit and should move both in lockstep — left for a separate decision.🤖 Generated with Claude Code
https://claude.ai/code/session_01C5zaYdMzMZAVhvuLWQqKWB