ci: add bun test workflow for pull requests

[Simplereally]

Description

Adds a GitHub Actions workflow to automatically run bun run test on pull requests targeting the main branch. This ensures that all tests pass before code is merged.

Type of change

• CI/CD (Infrastructure)

How Has This Been Tested?

• Verified workflow configuration.
• Ran bun run test locally to confirm all 1427 tests are passing.

Summary by CodeRabbit

• Chores
  • Added an automated testing workflow to improve code quality assurance during development.
  • Updated the declared package manager to a newer Bun version to align tooling across the project.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

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

Project	Deployment	Review	Updated (UTC)
bloomstudio	Ready	Preview, Comment	Jan 13, 2026 0:17am

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Added a new GitHub Actions workflow to run tests on pull requests and manual dispatch; updated packageManager version in package.json from bun@1.3.5 to bun@1.3.6.

Changes

Cohort / File(s)	Summary
CI workflow ​.github/workflows/test.yml	New GitHub Actions workflow "Test" added. Triggers: pull_request to main and workflow_dispatch. Runs on ubuntu-latest, checks out repo, sets up Bun v1.3.6, runs bun install --frozen-lockfile, then bun run test.
Package manifest package.json	Updated packageManager field from "bun@1.3.5" to "bun@1.3.6". No other changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 I hopped in the CI, neat and spry,
Bun warmed up beneath the sky,
Tests now bound to every PR,
Hooray — green checks not far! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'ci: add bun test workflow for pull requests' accurately describes the main change: adding a GitHub Actions workflow for running Bun tests on pull requests.
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.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fad3b7c and a2c09dc.

📒 Files selected for processing (2)

• .github/workflows/test.yml
• package.json

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/test.yml (2)

14-16: Consider pinning Bun to a specific version for reproducible builds.

Using bun-version: latest can cause unexpected CI failures when a new Bun version introduces breaking changes. Consider pinning to a specific version or using a version range.

♻️ Suggested improvement

       - uses: oven-sh/setup-bun@v2
         with:
-          bun-version: latest
+          bun-version: "1.x"

Alternatively, pin to a specific version (e.g., "1.1.42") for maximum reproducibility.

---

17-17: Consider using --frozen-lockfile to ensure lockfile integrity.

Adding --frozen-lockfile prevents accidental lockfile modifications in CI, ensuring the build uses exactly what's committed.

♻️ Suggested improvement

-      - run: bun install
+      - run: bun install --frozen-lockfile

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fba3dc2 and fad3b7c.

📒 Files selected for processing (1)

• .github/workflows/test.yml

🔇 Additional comments (1)

.github/workflows/test.yml (1)

1-18: Workflow structure looks good overall.

The workflow correctly triggers on pull requests to main and supports manual dispatch. The job steps follow a logical sequence: checkout → setup runtime → install dependencies → run tests. This is a clean and minimal CI setup.