fix: support-node-workspace-plugin-prerelease

[Animalmix55]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #2248 🦕

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Animalmix55]

@chingor13 tested and validated using my local branch of https://github.com/Seekr-io/release-please-action

[tada5hi]

@Animalmix55 shouldn't the version be incremented to x.x.x-beta.x instead of x.x.x-beta ?

[Animalmix55]

@Animalmix55 shouldn't the version be incremented to x.x.x-beta.x instead of x.x.x-beta ?

The initial prerelease comes with no .#, subsequent prereleases begin appending and iterating the .#.

I did not make any changes to the way that the prerelease version strategy operates, but I don’t disagree that it’s a bit unexpected. It appears you could make this happen by specifying a prerelease type of beta.1 since the prerelease type of the previous version is persisted on future bumps.

[niieani]

Looks good. Hope this gets merged!