Version updates (#99)

* Version updates.

* Version updates.

Author: rlubke

.github/workflows/node.js.yml

@@ -27,8 +27,8 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        node-version: [18.15.x, 19.x]
-        coherence-version: [22.06.10, 24.09]
+        node-version: [18.x, 19.x, 20.x, 21.x, 22.x, 23.x]
+        coherence-version: [22.06.11, 24.09]
 
     steps:
     - uses: actions/checkout@v3

.github/workflows/release.yml

@@ -25,7 +25,7 @@ jobs:
         with:
           ref: ${{ github.event.release.target_commitish }}
       # install Node.js
-      - name: Use Node.js 18.15.x
+      - name: Use Node.js 18.x
         uses: actions/setup-node@v3
         with:
           node-version: 18.15.x
@@ -37,7 +37,7 @@ jobs:
       - run: echo "/tmp/grpc/bin" >> $GITHUB_PATH
       - run: npm install
       # run unit tests
-      - run: COHERENCE_VERSION=22.06.10 npm run test-cycle
+      - run: COHERENCE_VERSION=22.06.11 npm run test-cycle
       - run: COHERENCE_VERSION=24.09 npm run test-cycle
       - run: npm install --no-save typedoc
       # generate dist which runs other tasks

DEVELOPING.md

@@ -44,7 +44,7 @@ The above can also be shortened to:
 However, if developing new functionality or tests, the manual start of the cluster using `coh-up` may be preferred as
 it avoids restarting the cluster allowing for quicker development times.
 
-**Important!** When calling `coh-up`, `test`, `coh-down`, or `test-cycle` the LTS version of Coherence will be used (`22.06.10`).
+**Important!** When calling `coh-up`, `test`, `coh-down`, or `test-cycle` the LTS version of Coherence will be used (`22.06.11`).
 To use a later Coherence version, such as `22.03`, prefix the calls with, or export `COHERENCE_VERSION=<desired-version>`.
 For example:
 ```bash

README.md

@@ -21,16 +21,16 @@ the network transport.
 Before testing the library, you must ensure a Coherence cluster is available.  For local development, we recommend using the Coherence CE Docker image; it contains everything necessary for the client to operate correctly.
 
 ```bash
-docker run -d -p 1408:1408 ghcr.io/oracle/coherence-ce:24.03
+docker run -d -p 1408:1408 ghcr.io/oracle/coherence-ce:24.09
 ```
 
 or to save some keystrokes/time, use the included npm script, `coh-up` to start a two-member Cluster with the gRPC port at 1408"
 ```bash
 npm run coh-up
 ```
 
-**Important!** When calling `coh-up` or `coh-down`, the LTS version of Coherence will be used (`22.06.10`).
-To use a later Coherence version, such as `24.03`, prefix the calls with, or export `COHERENCE_VERSION=<desired-version>`.
+**Important!** When calling `coh-up` or `coh-down`, the LTS version of Coherence will be used (`22.06.11`).
+To use a later Coherence version, such as `24.09`, prefix the calls with, or export `COHERENCE_VERSION=<desired-version>`.
 For example:
 ```bash
 COHERENCE_VERSION=24.03 npm run coh-up

bin/docker-utils.sh

@@ -7,7 +7,7 @@
 
 set -e
 
-declare VERSION=${COHERENCE_VERSION:=22.06.10}
+declare VERSION=${COHERENCE_VERSION:=22.06.11}
 declare TYPE=${COHERENCE_TYPE:=coherence-ce}
 declare REGISTRY=${DOCKER_REGISTRY:=ghcr.io/oracle}
 

bin/test-cycle.sh

@@ -10,7 +10,7 @@ set -e
 mkdir -p "${PWD}"/etc/cert
 chmod 777 "${PWD}"/etc/cert
 
-declare VERSION=${COHERENCE_VERSION:=22.06.10}
+declare VERSION=${COHERENCE_VERSION:=22.06.11}
 declare TYPE=${COHERENCE_TYPE:=coherence-ce}
 declare REGISTRY=${DOCKER_REGISTRY:=ghcr.io/oracle}
 declare LABEL=clear