v0.3.42: kb config defaults, downgrade nextjs

[waleedlatif1]

• improvement(kb): add fallbacks for kb configs (improvement(kb): add fallbacks for kb configs #1199)
• fix(deps): downgrade nextjs (fix(deps): downgrade nextjs #1200)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ready	Preview	Comment	Aug 30, 2025 4:49am
sim (staging)	Building			Aug 30, 2025 4:49am

[greptile-apps]

Greptile Summary

This PR introduces two main improvements to the codebase: adding fallback defaults for knowledge base configuration parameters and updating Next.js dependency versions across the monorepo.

The knowledge base configuration changes add defensive programming by providing sensible default values for all KB_CONFIG_* environment variables. These changes affect the document processing service (apps/sim/lib/knowledge/documents/service.ts) and background processing task (apps/sim/background/knowledge-processing.ts). The fallbacks include default timeouts (300s overall, 10s API), concurrency limits (20 concurrent documents), batch sizes (10-20), processing delays (100-200ms), and retry settings (3 attempts with exponential backoff). This ensures the knowledge base system continues functioning even when configuration environment variables are missing or undefined.

The dependency management changes involve updating Next.js versions from ^15.3.2 to ^15.4.1 across the monorepo. The root package.json adds version overrides for both next and @next/env packages, while apps/sim/package.json updates its direct dependencies and adds local overrides. These overrides force consistent Next.js versions across all workspace packages, preventing version conflicts that could arise from different packages resolving to different Next.js versions.

These changes integrate well with the existing codebase architecture. The knowledge base fallbacks follow established patterns already present in the service layer, maintaining consistency with the defensive programming approach. The dependency overrides align with the monorepo structure, ensuring all apps and packages use the same Next.js version for compatibility.

Confidence score: 3/5

• This PR has some inconsistencies that require careful review, particularly the contradiction between the description and actual changes
• Score reflects confusion about the Next.js version changes - PR claims "downgrade" but actually upgrades, potentially indicating incomplete resolution of stated compatibility issues
• Pay close attention to the Next.js dependency changes in both package.json files and verify the Bun compatibility claims

_{4 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}