`npm version` hook support: preversion, version, postversion

[semantic-release]

`npm version` hook support: preversion, version, postversion

[travi]

i typically use prepack to do tasks like building a bundle before publishing. i've also successfully used prepublishOnly, but prefer prepack because it runs when packing locally too. would those scripts accomplish what you're looking for?

[pvdlg]

What @travi described is the recommended approach.

For info, that's also mentioned in our FAQ: https://github.com/semantic-release/semantic-release/blob/caribou/docs/support/FAQ.md#how-can-i-use-a-npm-build-script-that-requires-the-packagejsons-version-

Please let us know if that answer your question, and close the issue if it does.

[imhoffd]

Thanks for your quick replies!

The root confusion to me is that some npm scripts during the release process appear to run, and some don't, which seems inconsistent.

• preversion/version/postversion would happen in the prepare step, if it was supported.
• prepublishOnly/prepack happen in the publish step.

---

As far as I can tell, since @semantic-release/git makes a release commit during the prepare step, there isn't an easy way of including file changes from the versioning step of the release process in the release commit.

[pvdlg]

The root confusion to me is that some npm scripts during the release process appear to run, and some don't, which seems inconsistent.

Well yes, the only npm command ran by @semantic-release/npm is npm publish. I guess we could use npm version to update the package.json. I can't remember why we made the choice of using custom code there. I'll look into it and see if we can switch to npm version.

As far as I can tell, since @semantic-release/git makes a release commit during the prepare step, there isn't an easy way of including file changes from the versioning step of the release process in the release commit.

I'm not sure I'm following...You can run @semantic-release/npm then @semantic-release/git so the updated package.json will be included in the commit. That's explained in this example.

[imhoffd]

I can't remember why we made the choice of using custom code there.

I'm guessing npm version isn't used because it does too much: it also makes a git tag and a commit, but I believe it can be disabled via npm --no-git-tag-version <version>.

[semantic-release-bot]

🎉 This issue has been resolved in version 5.1.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[imhoffd]

I'm not sure I'm following...

Yeah, sorry, that was written hastily.

I am running @semantic-release/npm before @semantic-release/git. package.json is being included in the commit. I was trying to explain that I can't use prepublishOnly/prepack because those run in the publish step, and the release commit is made in the prepare step. I have additional file changes needed during the prepare step before the release commit is made, but the only way to accomplish that was to use @semantic-release/exec.

---

I will try 5.1.0 😄