release-beta

To publish a beta release for multiple package.json files, you update both version fields to an identical X.Y.Z-beta.N string, commit the changes on main, create a v-prefixed tag matching the version, and push commits and tags to origin.

Mismatched beta versions occur when package.json files are updated manually. Automating the version bump ensures that both client and server package.json files receive the exact same beta version string before committing and tagging.

The correct git tag format for a beta version is a v-prefixed tag that exactly matches the version string in your package.json, such as v1.2.3-beta.1, which must be pushed to origin along with the commit.

Yes, an automated git workflow can commit the version bump directly to the main branch, create the matching v-prefixed beta tag, and push both the commits and tags to origin for a consistent beta release process.

Even if both package.json files are updated, you still need to commit the changes on main and create a v-prefixed tag matching the version to correctly publish the beta release, which can be fully automated to prevent tagging mistakes.