feat: adds release action

[pandeymangg]

Adds a github action for releasing the react-native sdk to npm when we push a release.
Fixes #15

Summary by CodeRabbit

• Chores
  • Added an automated workflow to publish the React Native SDK to npm when a new release is published.

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 801c660 to 38e8607.

Walkthrough

A new GitHub Actions workflow named "Release React Native SDK" has been added. It automates the process of building, testing, and publishing the React Native SDK package to npm whenever a GitHub release is published. The workflow includes steps for dependency installation, building, testing, and npm publishing with authentication.

Changes

File(s)	Change Summary
.github/workflows/release.yml	Added a workflow to automate building, testing, and publishing the React Native SDK to npm.

Assessment against linked issues

Objective	Addressed	Explanation
Automate release via GitHub Actions when a GitHub release is published (#15)	✅
Build the SDK as part of the release workflow (#15)	✅
Release the SDK on npm as part of the workflow (#15)	✅
Replace the package.json version number with the release version number as part of the workflow (#15)	❌	No step is present in the workflow to update package.json to match the GitHub release tag.

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes were found.

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (2)

.github/workflows/release.yml (2)

9-12: Add a concurrency block to prevent duplicate publishes.

When multiple releases are pushed in quick succession, parallel jobs can both reach npm publish, racing and failing. A one-liner avoids that:

  release:
    runs-on: ubuntu-latest
+    concurrency: release-${{ github.ref }}

---

22-27: Cache pnpm store to cut CI time by ~70 %.

actions/setup-node@v4 supports built-in caching; no extra steps needed.

      - name: Setup Node.js 20.x
        uses: actions/setup-node@v4
        with:
          node-version: 20.x
          registry-url: https://registry.npmjs.org
+         cache: 'pnpm'

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0c2b411 and 5652774.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

.github/workflows/release.yml (1)

16-21: Running on Node 22.x is risky – the current LTS is 20.x.

Node 22 is still “Current”; React-Native tool-chain and many deps are only tested on LTS lines (20/18). A surprise major-version break will block releases.

-          node-version: 22.x
+          # Use stable LTS
+          node-version: 20.x

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud