this way, on git tag, the CIs will upload the binaries, and we can then have a publish script that downloads all those binaries, packages them, and publishes the package w/ all that's needed
see if you can have multiple CIs upload binaries to the same release
it'll go like this:
commit to any branch
all CIs: test
push tag to any branch (is this exploitable?)
all CIs: test & create release draft, pushing their built artifacts
manual publish via npm publish, which the npm script does the whole packaging process
the publish script will use the npm version, and assume that it is the git tag, getting the binaries from there
on publish, the maintainers will edit the release and undraft it, marking it as a release or pre-release or whatever
sounds good, as it'll work for both releases and pre-releases
we can also keep the existing makefile scripts and such, since we don't want to use node-gyp to build the binary
https://github.com/tcnksm/ghr
this way, on git tag, the CIs will upload the binaries, and we can then have a publish script that downloads all those binaries, packages them, and publishes the package w/ all that's needed
see if you can have multiple CIs upload binaries to the same release
it'll go like this:
npm publish, which the npm script does the whole packaging processthe publish script will use the npm version, and assume that it is the git tag, getting the binaries from there
on publish, the maintainers will edit the release and undraft it, marking it as a release or pre-release or whatever
sounds good, as it'll work for both releases and pre-releases
we can also keep the existing makefile scripts and such, since we don't want to use node-gyp to build the binary