* 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>
The github action that generates the documentation fails currently due
to the fact that it's expecting the generated schema to exist, but it
does not exist unless it's explicitly built.
This commit adds `npm run build:schema` to the workflow action.
Signed-off-by: Lance Ball <lball@redhat.com>
The id of release was left out, so the checks to see if there needs to be a publish were being skipped
Signed-off-by: Lucas Holmquist <lholmqui@redhat.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>
This commits adds the release-please github action to automate the creation of release PR's
This is only for creating GH releases and they automation of publication to npm will come in the future
Signed-off-by: Lucas Holmquist <lholmqui@redhat.com>
This commit adds templates for GitHub issues and PRs, and a configuration
file for VSCode to enable build and test tasks in the IDE.
Signed-off-by: Lance Ball <lball@redhat.com>
* chore(actions): don't auto-close stale issues and pull requests
Open issues and pull requests should be closed by a human who has considered
the issue/pr and made a choice based on the content of the issue/pr and the
state of the repository.
What this means in practice is that some issues will stay open for a long
time, even if they are stale. They may be open because it really is something
that will be considered for future work. Periodic issue triage should be
done by the maintainers, and if an issue _should_ be closed - for example,
the issue is no longer relevant - then a maintainer can close it.
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
Remi Cattiau
Tim Nunamaker
Lance Ball
Jordan Moore