chore(deps): manage dependency versions using catalog

[JeanMeijer]

Description

Briefly describe what you did and why.

Screenshots / Recordings

Add screenshots or recordings here to help reviewers understand your changes.

Type of Change

• Bug fix
• New feature
• Breaking change
• UI/UX update
• Docs update
• Refactor / Cleanup

Related Areas

• Authentication
• Calendar UI
• Data/API
• Docs

Testing

• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Checklist

• I’ve read the CONTRIBUTING guide
• My code works and is understandable and follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• Any dependent changes are merged and published

Notes

(Optional) Add anything else you'd like to share.

By submitting, I confirm I understand and stand behind this code. If AI was used, I’ve reviewed and verified everything myself.

---

Summary by cubic

Centralized dependency versions with a root catalog so all packages use catalog: references instead of inline versions. This keeps versions consistent across the monorepo and makes upgrades simpler.

• Dependencies

  • Added a catalog to the root package.json and updated bun.lock.
  • Replaced inline versions with catalog: in workspace deps, devDeps, and peerDeps (e.g., next, zod, eslint, @trpc/server, ai, @types/node, @upstash/redis).
  • No runtime changes.

• Migration

  • To bump a shared dependency, edit the root catalog and run bun install.
  • For new packages, reference shared deps with catalog: instead of a version.

^{Written for commit a8f22dd. Summary will update on new commits.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
analog	Ready	Preview, Comment	Mar 25, 2026 1:08am

[cubic-dev-ai]

No issues found across 19 files