Files

Alex Crichton 30589170b4 More fixes for publish action (#5110 )

Looks like #5091 wasn't enough and some of the APIs needed updating with
changes made in the meantime. I've updated the action here and
additionally made a separate change where the release isn't continually
created and deleted but instead left alone and only the tag is updated.
This should work for the `dev` release and avoids deleting/recreating on
each PR, sending out notifications for new releases.

2022-10-24 17:59:37 -05:00

action.yml

Reduce warnings on CI from GitHub Actions (#5083 )

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

main.js

More fixes for publish action (#5110 )

2022-10-24 17:59:37 -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.