![Luc Georges](/assets/img/avatar_default.png)
* feat: add release CI * debug: disable `aarch64-unknown-linux-gnu` & add missing `pkgconfig` * fix: add `g++` & `pkg-config` * fix: install libssl-dev on ubuntu * fix: add sudo in specific case * fix: remove ssl dependency * feat: update Cargo.lock * fix: use gcc-multilib * fix: disable aarch64-linux for now * fix: disable problematic platforms * fix: comment out `aarch64-pc-windows-msvc` * fix: set allow deadcode for `Document.language_id` * fix: set valid release tag
22 lines
913 B
Markdown
22 lines
913 B
Markdown
# github-release
|
|
|
|
Copy-pasted from
|
|
https://github.com/rust-lang/rust-analyzer/tree/2df30e1e07eafc1de0359566423f471920693a34/.github/actions/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.
|