deps: bump fumadocs 16.15.8 and lucide-react 1.43.0 - #63
Merged
Merged
Conversation
Bump frontend direct deps only: fumadocs-core and fumadocs-ui to ^16.15.8 (lock 16.15.8), lucide-react to ^1.43.0 (lock 1.43.0). Leave fumadocs 16.15.9+, fumadocs-mdx 15, posthog-js, next 16.3.5, TypeScript 7, ESLint 10, and backend Python deps unchanged. Co-authored-by: Adam Xu <AdamEXu@users.noreply.github.com>
AdamEXu
marked this pull request as ready for review
September 15, 2026 15:47
Greptile SummaryThis PR updates three frontend dependencies and synchronizes their lockfile records.
Confidence Score: 5/5The PR appears safe to merge because the dependency graph is internally consistent and no actionable regression was identified. The changed manifest constraints and lockfile resolutions agree, declared peer requirements remain satisfied, and the reviewed build paths consume the frozen lockfile.
|
| Filename | Overview |
|---|---|
| frontend/package.json | Raises the minimum compatible versions for fumadocs-core, fumadocs-ui, and lucide-react without changing dependency-range strategy. |
| frontend/pnpm-lock.yaml | Consistently updates importer resolutions, package metadata, integrity hashes, peer links, and snapshots for the three dependency upgrades. |
Reviews (1): Last reviewed commit: "deps: bump fumadocs 16.15.8 and lucide-r..." | Re-trigger Greptile
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.
What & why
Daily frontend-only dependency bump for 2026-09-15. Supply-chain vetted packages published at least ~7 days ago as of 2026-09-15.
Bumped
fumadocs-core:^16.15.7/ lock16.15.7→^16.15.8/ lock16.15.8fumadocs-ui:^16.15.7/ lock16.15.7→^16.15.8/ lock16.15.8lucide-react:^1.41.0/ lock1.41.0→^1.43.0/ lock1.43.0Lockfile under
frontend/pnpm-lock.yamlupdated to match. No other files changed (backend/ untouched).Deferred (not bumped)
fumadocs-core/fumadocs-ui16.15.9+— too fresh (newer than the ~7-day publish floor;16.15.11is already on npm)fumadocs-mdxmajor 15 — historically deferred; stays on^14.3.2posthog-js— leave the existing constraint>=1.422.1 <1.425.0untouched (lock remains1.424.1)next/eslint-config-next16.3.5— too fresh; stay on16.3.4#62)Area
How tested
pnpm add fumadocs-core@16.15.8 fumadocs-ui@16.15.8 lucide-react@1.43.0infrontend/fumadocs-core@16.15.8,fumadocs-ui@16.15.8,lucide-react@1.43.0pnpm typecheckpassedpnpm buildpassed (Next.js 16.3.4 / Turbopack)pnpm lintstill fails on pre-existing app issues (setState-in-effect, unused vars, generated.source/files); none of those files changed in this PR. CI already treats lint as a non-blocking ratchet.Security checklist
@auth_requiredis applied to routes that need authentication. N/A — no backend route changes..env,*.db, keys, or credentials in the diff.Checks
cd frontend && pnpm lintpasses. (pre-existing failures; not introduced here)make dev-backend). N/A — backend/ untouched.