wasi-sdk

Commit Graph

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	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.	2 years ago

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.

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.

2 Commits (392035c16d5bbae37345ce729ddb2cc45e50ad87)