Skip to content

chore: update dependencies and release configuration#34

Merged
patrickkabwe merged 1 commit intomainfrom
fix/release-workflowv1
May 19, 2025
Merged

chore: update dependencies and release configuration#34
patrickkabwe merged 1 commit intomainfrom
fix/release-workflowv1

Conversation

@patrickkabwe
Copy link
Copy Markdown
Owner

@patrickkabwe patrickkabwe commented May 19, 2025

  • Added @semantic-release/git as a dev dependency in package.json and bun.lock.
  • Updated release.config.js to include @semantic-release/git for asset management.
  • Removed outdated notes from README.md regarding React Native version requirements.
  • Added a build step in the GitHub Actions workflow for the release process.

Summary by CodeRabbit

  • Chores
    • Updated release workflow to include a build step before releasing.
    • Added @semantic-release/git as a development dependency.
    • Enhanced release configuration to automatically commit package and changelog files during releases.
  • Documentation
    • Removed a redundant note about React Native version requirements from the README for clarity.

- Added `@semantic-release/git` as a dev dependency in `package.json` and `bun.lock`.
- Updated `release.config.js` to include `@semantic-release/git` for asset management.
- Removed outdated notes from `README.md` regarding React Native version requirements.
- Added a build step in the GitHub Actions workflow for the release process.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 19, 2025

Walkthrough

This update introduces a build step to the release workflow, adds the @semantic-release/git development dependency, and configures semantic-release to commit package.json and CHANGELOG.md during releases. It also removes a redundant note about React Native requirements from the documentation.

Changes

File(s) Change Summary
.github/workflows/release.yml Added a "Build lib" step running bun run build before the release step in the workflow.
README.md Removed a duplicated note about the React Native version requirement for Nitro Views.
package.json Added @semantic-release/git as a new devDependency.
release.config.js Configured semantic-release to use @semantic-release/git to auto-commit package.json and CHANGELOG.md.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Bun
    participant Semantic Release
    participant Git

    GitHub Actions->>Bun: bun install
    GitHub Actions->>Bun: bun run build
    GitHub Actions->>Semantic Release: Run release process
    Semantic Release->>Git: Commit package.json, CHANGELOG.md (via @semantic-release/git)
    Semantic Release->>GitHub Actions: Complete release
Loading

Poem

A bunny hops with nimble feet,
Now building first, before release is sweet.
With Git in tow for changelogs new,
The docs are tidied, clear for you.
Dependencies bloom, the workflow’s neat—
This hop brings progress, swift and fleet!
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
  • 📝 Generate Docstrings

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/release.yml (1)

50-50: Remove trailing whitespace.

Line 50 contains trailing spaces which triggered the YAMLlint warning.

-        
+
🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 50-50: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between fd9ef5d and 4decd47.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (4)
  • .github/workflows/release.yml (1 hunks)
  • README.md (0 hunks)
  • package.json (1 hunks)
  • release.config.js (1 hunks)
💤 Files with no reviewable changes (1)
  • README.md
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/release.yml

[error] 50-50: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Build Android Example App (new architecture)
  • GitHub Check: Build Android Example App (old architecture)
  • GitHub Check: Build iOS Example App (new architecture)
  • GitHub Check: Build iOS Example App (old architecture)
🔇 Additional comments (3)
package.json (1)

55-55: Good addition of the @semantic-release/git dependency.

The addition of this dependency aligns perfectly with the changes in the release configuration to automate committing package.json and CHANGELOG.md during releases.

.github/workflows/release.yml (1)

48-50: Good addition of the build step before release.

Adding the build step ensures that the library is properly compiled before releasing, which is essential for a complete and reliable release process.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 50-50: trailing spaces

(trailing-spaces)

release.config.js (1)

50-50: Good configuration of the semantic-release Git plugin.

The configuration correctly specifies package.json and CHANGELOG.md as assets to be committed automatically during the release process. This simplifies release management and ensures consistent versioning.

@patrickkabwe patrickkabwe merged commit ad47956 into main May 19, 2025
5 checks passed
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 0.4.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant