4 Commits (95e3c2c6c79367eae412db5833155f4a36582eed)

Author	SHA1	Message	Date
Andrew Brown	2345285702	ci: allow overriding script inputs from the environment ... When testing out these scripts on a fork, I realized that it was more convenient to use a single environment variable (e.g., `GITHUB_API_URL=... ci/draft-release.sh`) to change some of the script's input parameters.	2 years ago
Andrew Brown	4f678be2b7	ci: split out release check into `is-workflow-valid.sh` ... This change refactors the script logic that checks if a workflow in fact built the commit matching our release tag out into a separate script. This is mainly an improvement in clarity.	2 years ago
YAMAMOTO Takashi	1282456143	download-workflow-artifacts.sh: skip dist-ubuntu-latest (#307) ... Exclude dist-ubuntu-latest to prefer dist-ubuntu-bionic, which is compatible with wider distributions. cf. https://github.com/WebAssembly/wasi-sdk/pull/273#issuecomment-1373879491 https://github.com/WebAssembly/wasi-sdk/issues/303	3 years ago
Andrew Brown	22b1d89e64	ci: document and script the release process (#295) ... Previously, the release process for wasi-sdk was undocumented and manual. The `RELEASING.md` document in this commit describes the steps necessary to publish a new version of `wasi-sdk` as a GitHub release and provides helpful scripts to automate some of the steps. With this in place, a future change could add a workflow trigger that allows running the steps automatically in GitHub actions. Keeping the steps as scripts in the repository, however, allows developers to re-run steps themselves in the (likely) case that something goes awry.	3 years ago