docs: explain multiple branch release process

[matthewvolk]

What/Why?

Note

Let's leave this PR open as a draft and test-drive it the next time we need to cut a release to make sure it's 100% accurate before we approve + merge

The biggest gap with our current CONTRIBUTING.md is that it only briefly mentions “cutting new releases” with Changesets, but it doesn’t fully explain the two–branch process (first cutting on canary, then syncing and releasing integrations/makeswift).

Testing

N/A

Migration

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0ac2b24

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst-b2b	Ready	Preview	Comment	Sep 4, 2025 1:53am
catalyst-canary	Ready	Preview	Comment	Sep 4, 2025 1:53am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst	Ignored			Sep 4, 2025 1:53am
catalyst-au	Ignored			Sep 4, 2025 1:53am
catalyst-uk	Ignored			Sep 4, 2025 1:53am