* feat: add node 24 support
Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
* squash: fixes for running tests
Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
---------
Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
* chore: Update compatible node version
Signed-off-by: Tim Nunamaker <tim@vana.com>
* Add Node.js 21 to the CI matrix
Signed-off-by: Tim Nunamaker <tim@vana.com>
---------
Signed-off-by: Tim Nunamaker <tim@vana.com>
* feat!: remove node 12 and node 14
Node 12 has been EOL since the end of April 2022 and Node 14 just became EOL at the end of April 2023
Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
* Update CI action to node 18.x
Signed-off-by: Jordan Moore <1930631+OneCricketeer@users.noreply.github.com>
* doc: update README
Signed-off-by: Jordan Moore <1930631+OneCricketeer@users.noreply.github.com>
---------
Signed-off-by: Jordan Moore <1930631+OneCricketeer@users.noreply.github.com>
I don't think downloading to `/tmp` for each `npm test` is such a great
idea. This does mean that contributors to this repo will need to run the
following command once on their clone after this commit lands.
```
git submodule init
git submodule update
```
Signed-off-by: Lance Ball <lball@redhat.com>
GitHub will not set secrets in the environment when a pull request is submitted
from a forked repository. This commit modifies the CI workflow to only send
the report when the API token has been set. It also consolidates the two
workflows into a single one which shares coverage data between jobs.
Fixes: https://github.com/cloudevents/sdk-javascript/issues/190
Signed-off-by: Lance Ball <lball@redhat.com>
Lucas Holmquist