release-stable

To automate synchronized version bumps across client and server package.json files, this Skill enforces matching version strings in both files, commits the changes, and pushes a corresponding vX.Y.Z git tag to ensure consistent versioning across multi-repo projects.

Promoting a beta release to a stable version in CI/CD involves removing the beta suffix from the existing version string in package.json, applying the updated X.Y.Z version across repositories, and creating a matching git tag for the stable release.

Cutting a stable release with consistent git tagging requires updating package.json versions, committing the changes, and pushing a vX.Y.Z tag to the repository to make shipping predictable and synchronized.

The best way to handle multi-repo release engineering for Node.js projects is to apply an automated versioning workflow that enforces matching package.json version strings across repositories and pushes corresponding git tags.

You do not strictly need a CI/CD pipeline to use automated stable release bumps, but validating that the versioning workflow is applied consistently within CI/CD pipelines ensures predictable and synchronized stable releases.

Enforcing matching version strings in multi-repo projects ensures that client and server versions are bumped in lockstep, preventing version mismatches and making the stable release process predictable across the entire stack.