idb-connector - npm Package Compare versions

Comparing version 1.2.19-beta.0 to 1.2.19

package.json

		{
		"name": "idb-connector",
		"version": "1.2.19-beta.0",
		"version": "1.2.19",
		"description": "A Node.js DB2 driver for IBM i",
		@@ -34,2 +34,6 @@ "homepage": "https://github.com/IBM/nodejs-idb-connector",
		"main": "lib/db2a.js",
		"files": [
		"src/",
		"lib/"
		],
		"directories": {
		@@ -49,3 +53,3 @@ "lib": "lib",
		"devDependencies": {
		"@release-it/conventional-changelog": "^7.0.0",
		"@release-it/conventional-changelog": "^8.0.1",
		"bindings": "^1.5.0",
		@@ -57,3 +61,3 @@ "chai": "^4.3.6",
		"mocha": "^10.1.0",
		"release-it": "^16.1.0"
		"release-it": "^17.0.3"
		},
		@@ -60,0 +64,0 @@ "binary": {

README.md

		@@ -122,24 +122,2 @@ # Node.js iDB Connector for IBM i


		## Release

		To create a new release the developer first needs to run `release.sh`
		```sh
		./release.sh
		```

		This script will create a new release branch, run release-it, push the new branch upstream.

		From there the developer needs to:

		1) Open a pull request, have it approved by at least 1 reviewer, and merged into the master branch
		2) Create a new release and tag from the [GitHub Web UI](https://github.com/IBM/nodejs-idb-connector/releases/new) with the release and tag name matching the version number in package.json.


		After the release is created our Jenkins instance will:

		1) Build the package
		2) Update the GH release with the binary asset
		3) Publish the release to NPM

		## License
		@@ -146,0 +124,0 @@

.eslintrc.js

.release-it.json

binding.gyp

CHANGELOG.md

CONTRIBUTING.md

docs/README.md

release.sh

test/asyncStatementTest.js

test/connectionTest.js

test/dataTypes.js

test/misc.js

test/README.md

test/statementTest.js

test/syncStatementTest.js

lib/binding/Release/napi3-ibmi-ppc64/db2ia.node