Files

Alex Crichton 6917ba5ae9 Add package-lock.json for github-release action (#5091 )

A local github action we have has been broken for about a month now
meaning that the `dev` tag isn't getting updated or getting new
releases. This appears to be due to the publication of new versions of
these dependencies which are running into issues using one another. I
think I've figured out versions that work and have added a
`package-lock.json` to ensure we keep using the same versions.

2022-10-24 12:15:45 -05:00

action.yml

Reduce warnings on CI from GitHub Actions (#5083 )

2022-10-20 23:11:38 -05:00

main.js

ci: Remove "publish" step (#2936 )

2021-05-25 12:52:41 -05:00

package-lock.json

Add package-lock.json for github-release action (#5091 )

2022-10-24 12:15:45 -05:00

package.json

Add package-lock.json for github-release action (#5091 )

2022-10-24 12:15:45 -05:00

README.md

Migrate from Azure Pipelines to Github Actions (#474 )

2019-11-05 17:21:52 -08: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.