Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This essentially setup CI/CD as Github actions.
I took some inspirations from https://github.com/Level/leveldown/blob/master/.github/workflows/release.yml to automate the prebuilds.
The
test.yml
workflow test on a variety of platform and node version.See for example:
https://github.com/larriereguichet/alphacep-ref-napi/actions/runs/1530682216
The
release.yml
workflow create the prebuilds artefact create a Github release and publish the package to npm.See an example of release:
https://github.com/larriereguichet/alphacep-ref-napi/releases/tag/3.0.3
As for the next steps I would recommend to:
alphacep
organisation on npm (if not already):https://www.npmjs.com/org/create
https://www.npmjs.com/settings/nshmyrev/tokens
NPM_TOKEN
to the repository secrets:https://github.com/alphacep/ref-napi/settings/secrets/actions
Bump version number inpush a new tag to publish the new release:package.json
andHope it helps,
Cheers!