fix(CI): add bun setup

[ymc9]

Summary by CodeRabbit

• Chores
  • Updated build and deployment tooling to enhance the release process.

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

A new GitHub Actions step is added to .github/workflows/publish-release.yml to install Bun using oven-sh/setup-bun@v2 with the latest version. The step is positioned after Node.js setup and before dependency installation with pnpm.

Changes

Cohort / File(s)	Change Summary
GitHub Actions Workflow Update \.github/workflows/publish-release\.yml	Added new step to install Bun (oven-sh/setup-bun@v2 with latest version) in the CI/CD pipeline, positioned between Node.js setup and pnpm dependency installation.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify that Bun version latest is compatible with the existing Node.js and pnpm versions in the workflow
• Confirm that the placement of the Bun installation step doesn't cause conflicts with subsequent build steps
• Check if there are any environment variable or cache considerations with the new tooling

Poem

🐰 A bun so fresh, now in the release,
Our workflow sings with tooling peace,
From Node to Bun, the pipeline gleams,
Hopping faster through CI dreams! 🚀

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/ci-publish-bun

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6330c3b and 990fe6b.

📒 Files selected for processing (1)

• .github/workflows/publish-release.yml (1 hunks)

---

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

[claude]

Claude finished @ymc9's task —— View job

---

Pull Request Review

Reviewing PR #462: "fix(CI): add bun setup"

Todo List:

• Read and analyze the workflow file changes
• Review code quality and best practices
• Check for potential bugs or issues
• Assess performance considerations
• Evaluate security concerns
• Check test coverage impact
• Provide comprehensive feedback

---

Review Summary

Context: This PR appears to add Bun setup to the publish-release.yml workflow, similar to the existing setup in build-test.yml.

✅ Positive Aspects

1. Consistency: Adding Bun setup to the publish workflow maintains consistency with the build-test workflow
2. Runtime Testing: Having Bun available during publish ensures compatibility across multiple JavaScript runtimes
3. Minimal Change: The 5-line addition is focused and doesn't introduce unnecessary complexity

📝 Code Quality & Best Practices

Good:

• Uses the official oven-sh/setup-bun@v2 action
• Uses latest version which ensures current Bun features
• Follows the same pattern as the existing build-test workflow

Areas for Consideration:

• Version Pinning: Using bun-version: latest can introduce unpredictability. Consider pinning to a specific version for reproducible builds
• Step Positioning: The bun setup should be positioned after Node.js setup but before dependency installation

🔍 Potential Issues

1. Version Stability: bun-version: latest could break builds if a new Bun version introduces breaking changes
2. Usage Clarity: It's unclear from the workflow if Bun is actually being used in the publish process or just set up for compatibility testing

🛡️ Security Considerations

Low Risk: The changes use the official Bun setup action from oven-sh which is the standard and secure approach.

⚡ Performance Considerations

Minimal Impact: Adding the Bun setup adds ~10-30 seconds to the workflow but provides value for runtime compatibility testing.

🧪 Test Coverage

No Direct Impact: This change doesn't affect test coverage as it's purely CI infrastructure.

💡 Recommendations

1. Pin Bun Version: Consider using a specific version like bun-version: "1.x" for more predictable builds
2. Document Usage: If Bun is being used for specific steps, consider adding comments to clarify its purpose
3. Runtime Matrix: If testing multiple runtimes, consider using a matrix strategy similar to the Node.js version matrix

Overall Assessment

This is a low-risk, beneficial change that improves the CI pipeline's runtime compatibility. The implementation follows established patterns and uses trusted actions.

Approved ✅

[Copilot]

Pull request overview

This PR fixes a CI workflow issue by adding Bun setup to the publish-release workflow. The change is necessary because the build process (specifically the tests/bun package build script) requires Bun to be installed for code generation via bunx. This addition brings the publish-release workflow into alignment with the existing build-test workflow, which already includes Bun setup.

Key changes:

• Added Bun setup step to publish-release.yml workflow using oven-sh/setup-bun@v2 with latest version

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.