chore(frontend): bump katex to 0.18.6 - #60
Merged
Merged
Conversation
Pin frontend katex from ^0.18.5 to ^0.18.6 (lockfile 0.18.6). Leave 0.18.7 deferred as under the 7-day freshness window. Co-authored-by: Adam Xu <AdamEXu@users.noreply.github.com>
AdamEXu
marked this pull request as ready for review
September 13, 2026 15:36
Greptile SummaryThe frontend now uses KaTeX 0.18.6 for its existing math-rendering pipeline. The package declaration and lockfile move from 0.18.5 to 0.18.6. Confidence Score: 5/5This dependency-only change appears safe to merge. The manifest and lockfile agree on
|
| Filename | Overview |
|---|---|
| frontend/package.json | Raises the direct katex range to ^0.18.6. The matching lockfile keeps CI and container installs on 0.18.6. |
| frontend/pnpm-lock.yaml | Updates the root katex specifier, package key, checksum, and snapshot from 0.18.5 to 0.18.6. The lock entries stay consistent. |
Sequence Diagram
sequenceDiagram
participant Build as CI or container build
participant Pnpm as pnpm
participant Lock as pnpm-lock.yaml
participant App as Next.js app
participant Markdown as ReactMarkdown
participant Rehype as rehype-katex
Build->>Pnpm: pnpm install --frozen-lockfile
Pnpm->>Lock: Read katex 0.18.6 and checksum
Lock-->>Pnpm: Locked package metadata
Pnpm-->>Build: Install katex 0.18.6
App->>App: Load katex 0.18.6 stylesheet
App->>Markdown: Render chat Markdown
Markdown->>Rehype: Send parsed math nodes
Rehype-->>Markdown: Return KaTeX markup
Markdown-->>App: Show formatted math
Reviews (1): Last reviewed commit: "chore(frontend): bump katex to 0.18.6" | 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
Frontend-only dependency bump for KaTeX math rendering.
Supply-chain:
katex@0.18.6aged ≥7d (published 2026-09-05), OSV clean. Deferred0.18.7as <7d fresh (published 2026-09-06). Deferred lucide/next/react majors/fresh patches, fumadocs (already at 16.15.7), TypeScript 7, and ESLint 10.Bumped
katex:^0.18.5/ lock0.18.5→^0.18.6/ lock0.18.6Skipped (fresh, majors, or already current)
katex@0.18.7— under 7-day freshness window16.15.7lucide-react— leave at^1.41.0next— leave at16.3.4react/react-dom— leave at19.2.8Area
How tested
frontend/package.jsonand regeneratedfrontend/pnpm-lock.yamlwithpnpm add katex@0.18.6^0.18.6resolves tokatex@0.18.6(not0.18.7)0.18.6pnpm typecheckpassedpnpm buildpassed (Next.js 16.3.4 Turbopack production build)pnpm lintstill fails on pre-existing app issues (setState-in-effect, unused vars, generated.source/files); none of those files changed in this PRSecurity checklist
@auth_requiredis applied to routes that need authentication. N/A.env,*.db, keys, or credentials in the diff.Checks
cd frontend && pnpm lintpasses. (pre-existing failures; not introduced here)make dev-backend). N/A — no backend changes