Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions .release-it.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
{
"npm": {
"publish": false
},
"git": {
"requireBranch": "master",
"commitMessage": "chore: release ${version}"
},
"github": {
"release": true,
"autoGenerate": true,
"releaseName": "v${verison}"
}
}
16 changes: 16 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,7 @@
- [Tests](#tests)
- [Contributing](#contributing)
- [License](#license)
- [Release](#release)

# Introduction

Expand Down Expand Up @@ -97,3 +98,18 @@ Please read the [contribution guidelines](https://github.com/IBM/nodejs-itoolkit

# License
[MIT](https://github.com/IBM/nodejs-itoolkit/blob/master/LICENSE)


# Release

To generate a release use one of the npm scripts:

- patch release `npm run release`
- for other release types run `npm run release-it` which will prompt
you for the release type.

These scripts will bump the version number, make a release commit, tag the release, and finally create a github release if the user has `GITHUB_TOKEN` set.

Otherwise release-it will output a URL with all the fields pre-populated see the [release-it docs](https://github.com/release-it/release-it/blob/HEAD/docs/github-releases.md#manual).

After the release is published the [publish action](https://github.com/IBM/nodejs-idb-pconnector/blob/a4154bacf8e327e242c2d44e312079aea0690d8f/.github/workflows/publish.yml#L1) will publish to npm.
Loading