npm-version-script.js about .github

[Supereg]

The current beta publishing script builds around a work flow where each beta branch name includes the version number. This allows to easily develop multiple beta lines at the same time (or properly separate them).
What is unexpected? Or what should change?

[NorthernMan54]

I was going to take a look at the code, and see if it is possible to tweak it and stop the exit(1) in this scenario.

The scenario was publishing a release of node-pty-prebuilt-multiarch from a branch without the proper beta name format. I was thinking maybe the code should look at the package.json version and adjust it based on that as a fall back.

Or is the beta/alpha branch name check there as protection against other issues ?