Manually update version number in package.json to indicate 1.0.0-rc

[bookernath]

What/Why?

It's confusing to customers (and our telemetry) that the version number in package.json is still <1.0.

Manually updating it for now; once we are out of RC this will be set automatically by changesets or CI/CD.

Testing

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 36c5d36

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 Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
catalyst-canary	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 30, 2025 8:19pm

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
catalyst	⬜️ Ignored (Inspect)			Jan 30, 2025 8:19pm
catalyst-au	⬜️ Ignored (Inspect)			Jan 30, 2025 8:19pm
catalyst-soul	⬜️ Ignored (Inspect)			Jan 30, 2025 8:19pm
catalyst-uk	⬜️ Ignored (Inspect)			Jan 30, 2025 8:19pm

[github-actions]

⚡️🏠 Lighthouse report

Lighthouse ran against https://catalyst-canary-m8cmqz057-bigcommerce-platform.vercel.app

🖥️ Desktop

We ran Lighthouse against the changes on a desktop and produced this report. Here's the summary:

Category	Score
🟢 Performance	98
🟢 Accessibility	92
🟠 Best practices	78
🟠 SEO	82

📱 Mobile

We ran Lighthouse against the changes on a mobile and produced this report. Here's the summary:

Category	Score
🟠 Performance	85
🟢 Accessibility	92
🟠 Best practices	78
🟠 SEO	85