standard-version
standard-version copied to clipboard
Version not bumping
I have a remote instance (Jenkins) running the release script. That's been working fine but running it on a new instance is producing different results. The issue is that the bump part of the release script is not occurring. The script is literally the same and I'm using npm ci
to ensure the package versions are consistent.
Any thought on why this could produce different results running the same script on different systems? Are there some git repository expectations that might be missing? It produces the right tag it's just not bumping the version.
New instance output. Note the missing bump logs.
+ npm run release -- --release-as patch
> @mob/[email protected] release /var/lib/jenkins/workspace/commonjsmodule-publish_master
> standard-version "--release-as" "patch"
✔ outputting changes to CHANGELOG.md
✔ committing CHANGELOG.md
✔ tagging release v1.0.1
ℹ Run `git push --follow-tags origin master` to publish
Running locally.
$ npm run release -- --release-as major
> @mob/[email protected] release /Users/ralph.smith/Workspace/mobile
> standard-version "--release-as" "patch"
✔ bumping version in package.json from 1.0.0 to 1.0.1
✔ bumping version in package-lock.json from 1.0.0 to 1.0.1
✔ outputting changes to CHANGELOG.md
✔ committing package-lock.json and package.json and CHANGELOG.md
✔ tagging release v1.0.1
ℹ Run `git push --follow-tags origin master && npm publish` to publish
Here's a historical log from the old instance that's been working fine:
+ npm run release -- --release-as patch
> @mob/[email protected] release /var/jenkins_home/workspace/_commonjsmodule-publish_master_2
> standard-version "--release-as" "patch"
✔ bumping version in package.json from 0.1.0 to 0.1.1
✔ bumping version in package-lock.json from 0.1.0 to 0.1.1
✔ outputting changes to CHANGELOG.md
✔ committing package-lock.json and package.json and CHANGELOG.md
✔ tagging release v0.1.1
ℹ Run `git push --follow-tags origin master && npm publish` to publish