Skip to content

Commit

Permalink
docs: clarify node vs npm in FAQ (#1731) thanks @vegardok
Browse files Browse the repository at this point in the history
  • Loading branch information
vegardok committed Jan 15, 2021
1 parent 7581aa8 commit c571910
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/support/FAQ.md
Expand Up @@ -8,7 +8,7 @@ By default, only the published package will contain the version, which is the on

However, the [`@semantic-release/git`](https://github.com/semantic-release/git) plugin can be used to push the updated `package.json` as well as other files to the Git repository.

If you wish to only update the `package.json` and push via Git you can set the project to `"private": true,` within your `package.json` to prevent publishing to [npm](https://www.npmjs.com). This can be useful for using **semantic-release** with a non-node project.
If you wish to only update the `package.json` and push via Git you can set the project to `"private": true,` within your `package.json` to prevent publishing to [the npm registry](https://www.npmjs.com).

## How can I use a npm build script that requires the `package.json`’s version ?

Expand Down

0 comments on commit c571910

Please sign in to comment.