@acalcutt/node-pre-gyp-test
Advanced tools
Comparing version 1.0.12-rc.0 to 2.0.0-rc.0
# node-pre-gyp changelog | ||
## Unreleased - 2.0.0 | ||
## v2.0.0-rc.0 | ||
- Supported Node versions are now stable versions of Node 18+. We will attempt to track the [Node.js release schedule](https://github.com/nodejs/release#release-schedule) and will regularly retire support for versions that have reached EOL. | ||
@@ -5,0 +5,0 @@ - Fixed use of `s3ForcePathStyle` for installation [#650](https://github.com/mapbox/node-pre-gyp/pull/650) |
{ | ||
"name": "@acalcutt/node-pre-gyp-test", | ||
"description": "Node.js native addon binary install tool", | ||
"version": "1.0.12-rc.0", | ||
"version": "2.0.0-rc.0", | ||
"keywords": [ | ||
@@ -6,0 +6,0 @@ "native", |
@@ -12,2 +12,7 @@ # Instructions for making a release | ||
`prepatch`, `preminor`, and `premajor` start a new series of pre-releases while bumping the patch, minor, or major version. E.g. `premajor` with `--preid pre` would do a prerelease for a new major using the `-pre` suffix (i.e. it would be a new major with `-pre.0`) | ||
You can use `prerelease` to bump the version for a new pre-release version. E.g. you could run `npm version prerelease --preid pre --no-git-tag-version` to go from `-pre.0` to `-pre.1`. | ||
For regular versions, you can use `patch`, `minor`, or `major`. E.g. `npm version major --no-git-tag-version`. | ||
2. Update the changelog, which can be found in `CHANGELOG.md`. The heading must match `## <VERSION>` exactly, or it will not be picked up. For example, for version 1.0.11: | ||
@@ -14,0 +19,0 @@ |
Sorry, the diff of this file is not supported yet
186594