ci: release action

[saseungmin]

Summary by CodeRabbit

• Chores
  • Added an automated release workflow that installs dependencies and publishes packages to npm when changes are pushed to the main branch.

[coderabbitai]

Walkthrough

A new GitHub Actions workflow for automated releases is added. It triggers on pushes to the main branch, checks out code, runs a custom setup, installs dependencies with Bun, and uses Changesets to manage releases and publishing to npm with appropriate authentication.

Changes

File(s)	Change Summary
.github/workflows/release.yml	Added a GitHub Actions workflow for automated release, setup, dependency install, and publish.

Poem

Hop, hop, a workflow new,
Releases now come right on cue!
With Bun and Changesets in the mix,
Our code deploys with clever tricks.
On every push to main we cheer,
The rabbit’s magic—release is here! 🐇✨

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[cloudflare-workers-and-pages]

Deploying react-native-youtube-bridge with    Cloudflare Pages

Latest commit:	e62bc27
Status:	✅  Deploy successful!
Preview URL:	https://131e73e1.react-native-youtube-bridge.pages.dev
Branch Preview URL:	https://ci-release.react-native-youtube-bridge.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

.github/workflows/release.yml (4)

1-7: Review workflow triggers
Triggers on push to the main branch will run the release on every merge. Consider refining the trigger to run on tag creation (e.g., on: push: tags: - 'v*.*.*') if you want to separate versioned releases from ordinary merges.

---

8-8: Enhance concurrency control
Current concurrency key queues overlapping runs by default. To automatically cancel in-progress workflows when a new one is triggered, add:

concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

---

21-23: Consider caching dependencies
Running bun install on every run can increase CI time. Add an actions/cache@v3 step to cache ~/.bun (and optionally node_modules) keyed by the bun.lockb hash.

Apply this diff:

+      - name: Cache Bun dependencies
+        uses: actions/cache@v3
+        with:
+          path: |
+            ~/.bun
+            node_modules
+          key: bun-${{ runner.os }}-${{ hashFiles('bun.lockb') }}
+          restore-keys: |
+            bun-${{ runner.os }}-

---

24-31: Verify Changesets action configuration

• Confirm you’re using the correct changesets/action version (v1 vs. any newer beta).
• Ensure your package.json defines a release script (bun run release) before invoking it.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf779ee and e62bc27.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

.github/workflows/release.yml (2)

15-17: Approve pinned checkout action
Using actions/checkout@v4 is a good practice to avoid unexpected breaks from major version bumps.

---

18-20: Verify custom setup action
Ensure that .github/actions/setup contains a valid action.yml and reliably installs Bun or other required tools on the runner before usage.