specmatic 1.0.3 → 1.2.1

package/.github/workflows/publish.yml

@@ -14,7 +14,7 @@ jobs:
           node-version: 14
       - run: npm install
       - run: npm run build
-      - uses: reedyuk/npm-version@1.2.1
+      - uses: reedyuk/npm-version@1.2.2
         with:
           version: ${{ github.event.release.tag_name }}
       - uses: JS-DevTools/npm-publish@v2

package/.github/workflows/test.yml

@@ -9,7 +9,7 @@ jobs:
     test:
         strategy:
           matrix:
-            node-version: [14.x, 16.x, 18.x, 20.x]
+            node-version: [16.x, 18.x, 20.x]
             os: [ubuntu-latest, windows-latest, macos-latest]
         runs-on: ${{ matrix.os }}
         steps:

package/CONTRIBUTING.MD

@@ -43,8 +43,8 @@ Finally commit
 * Push access to master branch 
 * Node version 14 or higher
 
-### Step 1: Update specmatic core jar
-If there is a new version available in [latest github release](https://github.com/znsio/specmatic/releases/latest), download it in the project root, replacing the older version. Commit the new version.
+### Step 1: Updating specmatic jar version
+If the specmatic jar version is to be updated, modify the __specmaticVersion__ property in __package.json__ accordingly and check it in.
 
 ### Step 2: Make a release via github releases
 * Goto [github releases](https://github.com/znsio/specmatic-node/releases) and draft a new release

package/README.md

@@ -53,7 +53,7 @@ Specmatic JS library exposes some of the commands as methods that can be run pro
 ```javascript
 import {
     startHttpStub,
-    setHttpStubExpecations,
+    setHttpStubExpectations,
     stopHttpStub,
     test,
     showTestResults,

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "specmatic",
-  "version": "1.0.3",
-  "specmaticVersion": "1.0.3",
+  "version": "1.2.1",
+  "specmaticVersion": "1.2.1",
   "description": "Node wrapper for Specmatic",
   "main": "dist/index.js",
   "scripts": {