chore: enter prerelease mode (rc) to ship v4.5.0-rc.0

[ericallam]

Summary

Adds .changeset/pre.json to put the repo into changesets pre mode with dist-tag rc. After this merges, the changesets bot regenerates the existing release PR as chore: release v4.5.0-rc.0. Merging that PR publishes the first release candidate of 4.5.0 to npm under @rc.

The pre-mode plumbing landed in #3628. The release content (chat.agent + sessions + ai prompts + dashboard server-changes) landed in #3629.

What ships when the bot PR merges

Under dist-tag rc:

• @trigger.dev/{sdk,core,build,react-hooks,redis-worker,plugins,python,rsc,schema-to-json}@4.5.0-rc.0
• trigger.dev@4.5.0-rc.0

Plus:

• Docker image ghcr.io/triggerdotdev/trigger.dev:v4.5.0-rc.0 (immutable tag only — :v4-beta is not touched)
• Helm chart oci://ghcr.io/triggerdotdev/charts/trigger.dev:4.5.0-rc.0
• GitHub release v4.5.0-rc.0 marked as Pre-release (no Latest badge)

What does NOT happen:

• npm latest stays at 4.4.6
• No marketing-site changelog PR (gated on is_prerelease != 'true')
• Docker :latest not touched (we never push it anyway in this repo)

Iteration

For subsequent rc.N: add a regular changeset to main, bot regenerates the release PR as v4.5.0-rc.N. Merge to ship.

Exiting pre mode

When ready to ship stable: pnpm exec changeset pre exit, push, merge regenerated PR. That publishes 4.5.0 under latest and fires the marketing-site dispatch.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b0022f3

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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 935a2648-d09c-4d98-9d9c-f7810bbe5ce8

📥 Commits

Reviewing files that changed from the base of the PR and between eedde27 and b0022f3.

📒 Files selected for processing (1)

• .changeset/pre.json

📜 Recent review details

⏰ 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). (4)

• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (actions)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

.changeset/pre.json (1)

1-22: LGTM!

---

Walkthrough

This PR adds a single configuration file, .changeset/pre.json, to the repository. The file configures pre-release versioning with mode "pre" and tag "rc". It records initial versions for multiple packages including coordinator, docker-provider, kubernetes-provider, supervisor, webapp, and several @trigger.dev/* scoped packages. The changesets array is initialized as empty.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: entering prerelease mode to ship v4.5.0-rc.0, which aligns with the single file modification adding the .changeset/pre.json configuration.
Description check	✅ Passed	The description provides excellent context on the change's purpose, what will be published, what won't change, and iteration workflow, though it doesn't follow the provided template structure with specific sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/enter-rc-pre-mode

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.