build: Add in base patch changeset to get a version number live

[nicholas-codecov]

Description

It seems like we need a base changeset present for the pre-release stuff to work properly.

[codecov]

This code review is regarding a version change on several packages in the repository. The change sees the versions of multiple packages being edited from 0.0.1 to 0.0.0. It is suspect because typically versions increase or advance, not decrease.

[codecov]

Reversing the version number from 0.0.1 to 0.0.0 might not be a good idea as it is typically used to signify nonexistence of a version. Consider changing this to at least the initial base version 0.0.1 or higher as appropriate.

[codecov]

Decreasing the version number could cause confusion or misinterpretation regarding the package's maturity or status. Keeping or increasing the version would be more aligned with common practices.

[codecov]

Changing the version to 0.0.0 may also cause compatibility issues with dependencies consuming this package expecting at least 0.0.1.

[codecov]

Avoid setting the version to 0.0.0. Instead, if this represents a pre-release version, consider a versioning scheme like 0.0.1-alpha.1 or similar.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9b9d8e8) 83.52% compared to head (ac20484) 83.52%.

Additional details and impacted files

Components	Coverage Δ
Plugin core	96.33% <ø> (ø)
Rollup plugin	7.35% <ø> (ø)
Vite plugin	7.35% <ø> (ø)
Webpack plugin	33.33% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.