fix: pin @base-ui/react to 1.4.1 to unblock builds broken by 1.6.0

[rohilsurana]

Problem

@base-ui/react@1.6.0 (published 2026-06-18) removed the flat OTPFieldPreview export — the otp-field module now only exposes the OTPField namespace. @raystack/apsara (all published versions, including 1.0.1) still imports OTPFieldPreview and declares "@base-ui/react": "^1.4.1".

Any fresh install of chronicle therefore resolves base-ui 1.6.0 and fails to build:

[MISSING_EXPORT] Error: "OTPFieldPreview" is not exported by "node_modules/@base-ui/react/otp-field/index.mjs"

This is why the Docker smoke-test CI has failed on every run since June 18 (last green: June 12). The Docker test installs a packed chronicle tarball into a fresh project, so the repo lockfile does not apply.

Upstream issue: raystack/apsara#843

Fix

Pin @base-ui/react to 1.4.1 as a direct dependency of chronicle. Bun dedupes apsara's transitive ^1.4.1 range to the pinned version, even when chronicle is installed from a packed tarball into a fresh project.

The pin can be dropped once apsara ships an OTP field compatible with base-ui 1.6 (or caps its range).

Verification

Replicated the Docker CI flow locally:

• bun pm pack → fresh bun init project → bun add ./chronicle.tgz: lockfile resolves a single @base-ui/react@1.4.1.
• bunx chronicle build --config examples/basic/chronicle.yaml --preset bun (the exact step that fails in CI): build completes.
• Started the built server with bun: docs page and /api/health return 200.
• Repo checks: bun test (180 pass), bun run lint (unchanged), bun run build:cli all green. Lockfile diff is one line.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
chronicle	Ready	Preview, Comment	Jul 3, 2026 4:53am

[coderabbitai]

Warning

Review limit reached

@rohilsurana, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b58dcac0-2d5f-4793-9edf-35cbccd4d77e

📥 Commits

Reviewing files that changed from the base of the PR and between f1c3a05 and 0409bcf.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• packages/chronicle/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/pin-base-ui-react

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[rohilsurana]

fixed in #154