Repository navigation
chore(deps): bump eight npm packages in one branch - #73
Merged
Merged
Conversation
Dependabot opened #71 (production, 2) and #72 (development, 6) against the same base. Merging them one at a time would make the other wait for a rebase and burn a second CI round, so consolidate both into a single green tree. - Production: idb 8.0.3 -> 8.0.4, lucide-react 1.49.0 -> 1.52.0 - Development: @types/node 26.6.3 -> 26.6.4, @vitejs/plugin-react 6.1.1 -> 6.1.2, jsdom 30.1.1 -> 30.1.2, oxlint 1.86.0 -> 1.87.0, shadcn 4.21.0 -> 4.21.4, vite 8.3.1 -> 8.3.3 - All minor or patch; the rest of the lock diff is transitive - The branches merged without conflict, so the lock is the exact union of the #71 and #72 locks with no regeneration and no drift - Gates on the merged tree: lint clean (same 7 warnings as main), build passes (main JS 520.06 -> 520.01 kB), 199 tests pass, and vitest run --coverage passes Closes #71 Closes #72 Tags: #deps #dependabot Co-Authored-By: htjulia <htjulia1@gmail.com>
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
1 participant
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.
Why
Dependabot opened #71 (production, 2 updates) and #72 (development, 6 updates) against the same base. Both touch
package.jsonandpackage-lock.json, so merging one would force a rebase and a second CI round on the other. This consolidates both into a single green tree.What
idblucide-react@types/node@vitejs/plugin-reactjsdomoxlintshadcnviteLock integrity
The two Dependabot branches merged with no conflicts, so the lock is the exact union of the #71 and #72 locks. It was not regenerated, so nothing drifted past what Dependabot pinned (
lucide-reactstays at 1.52.0).Verification (merged tree)
npm ci: OKnpm run lint: exit 0, 7 warnings, the sameonly-export-componentsset asmainnpm run build: passes. Main JS 520.06 -> 520.01 kB (gzip 164.28 -> 164.27)npm test: 17 files, 199 tests passnpx vitest run --coverage: 199 tests passci-completeon their ownNot introduced by this PR
npm auditreports the same 16 findings on this branch as onmain(critical 1, high 11, moderate 4), all on dev-only paths.npm audit --omit=devreports 0.Closes #71
Closes #72