feat: RC with correct version number

[marcus-pousette]

Describe the bug
If I am to release a major update, I expect the release candidate to be something like

1.0.0-hash

but now the rc seems to just use the manifest version.

so I get something like

0.x.y-hash

Is the feasible to fix? I guess this would need to integrate with some semantic release library to predict the next version

[achingbrain]

This is almost certainly fixable if you want to take a stab at it.

So far it's been good enough to just recommend people use the @next tag to install an RC and to not worry about the version number too much but it might give a bit more predictability to properly generate the next release version number.

I would class this as a "nice to have" though.