chore: bump up nitro

[patrickkabwe]

Summary by CodeRabbit

• Chores
  • Updated the version range for "react-native-nitro-modules" to allow for newer compatible releases.

[coderabbitai]

Walkthrough

The dependency version for "react-native-nitro-modules" in the example project's package.json was updated from a fixed version to a caret-based range, allowing for automatic adoption of future compatible releases starting from version 0.26.3.

Changes

File(s)	Change Summary
example/package.json	Updated "react-native-nitro-modules" dependency from "0.26.2" to "^0.26.3"

Possibly related PRs

• chore(deps): update nitro-codegen and react-native-nitro-modules to v… #51: Updates the "react-native-nitro-modules" dependency version in example/package.json, similar to this PR's focus.
• feat: new-nitro #28: Also modifies the version specification for "react-native-nitro-modules" in example/package.json, relating to dependency management.

Suggested labels

released on @next

Poem

A hop, a skip, a caret’s leap,
To newer versions we now keep.
No longer locked, we’re free to roam,
With patch and minor updates home.
The garden grows, dependencies bloom—
A rabbit’s cheer for version room! 🥕✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 337d98c and 3e13409.

📒 Files selected for processing (1)

• example/package.json (2 hunks)

🔇 Additional comments (1)

example/package.json (1)

16-16: Ensure the move to a caret range is intentional and lockfile is regenerated

Switching from a pinned 0.26.2 to ^0.26.3 means any 0.26.x and future 0.26.y releases will be installed automatically. This can silently pull in breaking changes if the library’s SemVer discipline slips.
• Run your CI/test suite after a clean install to verify compatibility.
• Commit the updated package-lock.json/yarn.lock so everyone resolves to the same version.
• If reproducible builds are critical, consider tilde (~) or keeping the exact version.

---

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.

[github-actions]

🎉 This PR is included in version 1.1.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀