Version number updated in package.json and package-lock.json instead of package.json in pkgRoot

[semantic-release]

Version number updated in package.json and package-lock.json instead of package.json in pkgRoot

[pvdlg]

I think this is because the package.json is updated in the prepare step and in your configuration the pkgRoot applies only to the publish step.
You should configure pkgRoot directly under release so it would apply to each step:

{
"release": {
    "noCi": true,
    "tagFormat": "${version}",
    "pkgRoot": "dist"
  }
}

[pvdlg]

The way plugin option works is explained here: https://semantic-release.gitbooks.io/semantic-release/content/docs/usage/plugins.html#configuration

Not sure if it's really clear, but I don't know how to improve. Feel free to propose improvements.

[pterblgh]

Thank you @pvdlg, this tip solved my issue.

This may be documented somewhere in the docs and I was the one who could not find it, but for a beginner (I've got familiar with semantic-release just today) like me it was totally unclear that steps have "side effects" in configuration setup.

Thank you again!

[EvanCarroll]

@pvdlg well, one question I have is that in order to build into dist/ you have to run ng build. I assume this is done before semantic release is run. If you do this, how do you bump the version that was produced in dist and the version that is in the source? That's what I was trying to do:

1. run ng build to populate dist
2. run semantic-release to bump the version number in dist.
3. run a postpublish script to sync the bumped version back to the source.
4. run semantic-release/git to push that back to the repo.

Or is there another method of doing this....

From what I can see, even if I could have a different pkgroot for bumping the version number and publishing the package, it wouldn't work: what I really need is for the version number to be set in dist and the source, before publication.