rust/compiler/rustc_codegen_cranelift/.github/actions/github-release
bjorn3 a8697f9565 Merge commit 'ef07e8e60f994ec014d049a95591426fb92ebb79' into sync_cg_clif-2023-04-29 2023-04-29 12:00:43 +00:00
..
README.md Merge commit 'ef07e8e60f994ec014d049a95591426fb92ebb79' into sync_cg_clif-2023-04-29 2023-04-29 12:00:43 +00:00
action.yml Merge commit 'ef07e8e60f994ec014d049a95591426fb92ebb79' into sync_cg_clif-2023-04-29 2023-04-29 12:00:43 +00:00
main.js Merge commit 'ef07e8e60f994ec014d049a95591426fb92ebb79' into sync_cg_clif-2023-04-29 2023-04-29 12:00:43 +00:00
package-lock.json Merge commit 'ef07e8e60f994ec014d049a95591426fb92ebb79' into sync_cg_clif-2023-04-29 2023-04-29 12:00:43 +00:00
package.json Merge commit 'ef07e8e60f994ec014d049a95591426fb92ebb79' into sync_cg_clif-2023-04-29 2023-04-29 12:00:43 +00:00

README.md

github-release

An action used to publish GitHub releases for wasmtime.

As of the time of this writing there's a few actions floating around which perform github releases but they all tend to have their set of drawbacks. Additionally nothing handles deleting releases which we need for our rolling dev release.

To handle all this this action rolls-its-own implementation using the actions/toolkit repository and packages published there. These run in a Docker container and take various inputs to orchestrate the release from the build.

More comments can be found in main.js.

Testing this is really hard. If you want to try though run npm install and then node main.js. You'll have to configure a bunch of env vars though to get anything reasonably working.