fix(release): install deps before merging macOS updater manifests

[aaditagrawal]

What

Adds `bun install --frozen-lockfile` between `Setup Node` and `Download all desktop artifacts` in the `Publish GitHub Release` job.

Why

The release job failed on `main` (run 24624988376) with:

```
error: Cannot find module '@effect/platform-node/NodeServices' from
/home/runner/work/t3code/t3code/scripts/merge-update-manifests.ts
```

`scripts/merge-update-manifests.ts` imports from `@effect/platform-node` — no `node_modules` present on the release runner means the import can't resolve. Upstream's release job includes an `Install dependencies` step before `Download all desktop artifacts`; fork's simplified flow dropped it when we stripped the nightly/npm-publish steps.

Test plan

• Kick off `Release Desktop` workflow after merge — `Merge macOS updater manifests` step should succeed.

Summary by CodeRabbit

• Chores
  • Enhanced release pipeline to ensure dependencies are properly installed during the publication stage.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f8650026-aa92-43c6-8416-22ca336a9345

📥 Commits

Reviewing files that changed from the base of the PR and between 52e015c and 3e54dc3.

📒 Files selected for processing (1)

• .github/workflows/release.yml

---

📝 Walkthrough

Walkthrough

Added an explicit dependency installation step to the GitHub Actions release workflow. The release job now runs bun install --frozen-lockfile after setting up Bun and Node, ensuring dependencies are available before artifact download and release publishing steps.

Changes

Cohort / File(s)	Summary
Release Workflow Configuration .github/workflows/release.yml	Added explicit bun install --frozen-lockfile step to the release job to ensure dependencies are installed before downstream artifact and publishing operations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Remove CLI npm publish from release workflow #13: Modifies the same release workflow file and adjusts the release job configuration by removing the publish_cli job dependency.

Suggested labels

vouch:trusted, size:M

Poem

🐰 A hop and a skip, with bun we install,
In the release job, dependencies answer the call,
Locked and bundled, so steady and true,
Before publishing code to the world anew,
One tiny step, a safeguard of care,
The release flows smoothly through the air! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: adding a dependency installation step before merging macOS updater manifests in the release workflow.
Description check	✅ Passed	The description includes all required sections from the template ('What Changed' and 'Why') with clear explanations and a test plan. UI Changes section is appropriately omitted as not applicable.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-workflow-install

---

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 and usage tips.}