chore(deps): update effect beta and Firebase dependencies

[fwal]

Summary

Routine dependency refresh on the next track, rebased onto next's pnpm catalog setup. Centralised versions are bumped in the catalog: block of pnpm-workspace.yaml; the two non-catalogued deps are bumped inline. Deliberately holds back major bumps that would break the current stack.

Updated — catalog (pnpm-workspace.yaml)

Dependency	From	To
effect / @effect/platform-browser / @effect/vitest	4.0.0-beta.90	4.0.0-beta.94
firebase	^12.9.0	^12.16.0
firebase-functions	^7.0.0	^7.2.5
firebase-admin	^13.6.0	^13.7.0

Updated — inline (not catalogued)

Dependency	From	To
@google-cloud/functions-framework (root + example/backend)	^5.0.x	^5.0.5
firebase-tools (root)	^15.5.1	^15.22.4

Docs

• Corrected a stale tailwind-merge version in example/app/AGENTS.md (^2.5.5 → ^3.4.0) so it matches the actual dependency.

Held back (intentionally)

• firebase-admin 13 → 14 — firebase-functions@7.2.5 still declares its peer range as ^11 || ^12 || ^13, so adopting admin v14 would violate the peer contract.
• Majors deferred to their own PRs: nx 22→23, vite 7→8, typescript 5.9→7.0, tailwindcss 3→4, @types/node 20→26.

Verification

• pnpm build — all projects build ✅
• pnpm test — all tests pass ✅
• pnpm lint — passes (pre-existing unrelated warnings only) ✅

No source migration was required for the effect beta jump.

🤖 Generated with Claude Code

[coderabbitai]

📝 Walkthrough

Walkthrough

Dependency versions are updated across the workspace catalog, root package manifest, backend example manifest, and app dependency documentation.

Changes

Dependency version bumps

Layer / File(s)	Summary
Workspace catalog version updates pnpm-workspace.yaml	Effect and Firebase catalog pins are updated; the Express pin remains unchanged.
Manifest and dependency documentation updates package.json, example/backend/package.json, example/app/AGENTS.md	Functions Framework, Firebase Tools, and Tailwind Merge version requirements are updated.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• fwal/effect-firebase#49: Both changes update or use dependency entries in pnpm-workspace.yaml’s catalog.

Poem

A bunny checks the pins in line,
Effect and Firebase now align.
Functions hop to versions new,
Tailwind follows neatly too.
The workspace blooms—what a fine view!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main dependency updates to Effect beta and Firebase packages.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

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.}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e025e47

Command	Status	Duration	Result
nx affected -t lint test build	✅ Succeeded	1m 21s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-07-10 06:44:39 UTC

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@example/app/package.json`:
- Around line 14-16: The dependency versions in the package manifest are out of
alignment because tailwind-merge is still set to the newer range instead of the
required one. Update the tailwind-merge entry in the same dependencies block
where class-variance-authority and clsx are listed so it is pinned to ^2.5.5,
keeping the rest of the package versions unchanged.

In `@example/backend/package.json`:
- Around line 15-17: The firebase-admin dependency range in package.json is
inconsistent with the root package version, so align the example/backend
declaration with the same ^13.7.0 range used elsewhere. Update the
firebase-admin entry in this package manifest only, keeping the rest of the
dependencies unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7fd963c9-ecbf-498f-b3d1-94a441523609

📥 Commits

Reviewing files that changed from the base of the PR and between d0e0669 and 743d1c6.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (8)

• example/app/package.json
• example/backend/package.json
• example/shared/package.json
• package.json
• packages/admin/package.json
• packages/client/package.json
• packages/effect-firebase/package.json
• packages/mock/package.json