chore(packages): leave changesets prerelease mode

[ericallam]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3b6d898

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

A single configuration change was made in .changeset/pre.json: the "mode" field was updated from "pre" to "exit". All other fields (including "tag", "initialVersions", and "changesets") are unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Single-file, single-field config toggle with no logic changes or ripple effects; fully homogeneous edit.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 132008f and 3b6d898.

📒 Files selected for processing (1)

• .changeset/pre.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

.changeset/pre.json (1)

2-2: Changesets prerelease‐exit checks – manual verification required

The .changeset/pre.json mode is correctly set to exit, but please confirm the following before merging:

• Packages currently still on prerelease versions (these will be bumped to GA when you run changeset version):
– packages/trigger-sdk (4.0.0-v4-beta.28)
– packages/schema-to-json (4.0.0-v4-beta.28)
– packages/rsc (4.0.0-v4-beta.28)
– packages/redis-worker (4.0.0-v4-beta.28)
– packages/react-hooks (4.0.0-v4-beta.28)
– packages/python (4.0.0-v4-beta.28)
– packages/cli-v3 (4.0.0-v4-beta.28)
– packages/core (4.0.0-v4-beta.28)
– packages/build (4.0.0-v4-beta.28)

• Dependencies pinned to prerelease ranges (they should flip to stable on exit):
– @trigger.dev/core in trigger-sdk, rsc, redis-worker, react-hooks, python, cli-v3, build
– @trigger.dev/build in rsc, python, cli-v3
– @trigger.dev/sdk in python
– @trigger.dev/schema-to-json in cli-v3

• No .changeset/*.md files were detected. If you intended to include release notes or bump annotations, please add them now.

• No CI workflows invoking changeset version or changeset publish were found under .github/workflows. Ensure your release pipeline runs these steps so that the exit prerelease bump is applied and pre.json is cleaned up automatically.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changesets/exit-v4-beta-prerelease

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.