The CI publish workflow uses a regexp to find-and-replace the version number in the package.json file. This caused the last publish run to change the version script instead of the version number.
- Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
You could try using the npm version command instead so the package.json is updated correctly.
I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project
Summary
The CI publish workflow uses a regexp to find-and-replace the version number in the package.json file. This caused the last publish run to change the
versionscript instead of the version number.You could try using the
npm versioncommand instead so the package.json is updated correctly.