Release Process

To publish a new version of wasi-sdk as a GitHub release:

Tag a commit with an annotated tag. Note that this must be an annotated tag, not a lightweight tag, so that version.sh can use it for calculating the package version (use git show wasi-sdk-... to show other tag messages).
```
TAG=wasi-sdk-1
git tag -a $TAG
git push origin $TAG
```
Find a successful workflow that CI has run for the tag. That successful workflow run will have build artifacts that need to be attached to the release. One could search around in the GitHub actions, but the following script will list completed workflows for a tag (get a token here):
```
ci/get-workflows-for-tag.sh $TAG $GITHUB_TOKEN
```
Download and unzip the workflow artifacts. Note that artifacts with +m or .m suffixes indicate that the Git tree was modified. Expect some duplicates since some of the same artifacts are built on multiple CI runners (e.g., Windows, MacOS, Linux). The following script does all of this automatically:
```
ci/download-workflow-artifacts.sh $TAG $WORKFLOW_RUN_ID $GITHUB_TOKEN
```
Draft a new release. This could be done manually but the following script simplifies the uploading of all the files and auto-generates the release description:

ci/draft-release.sh $TAG $ARTIFACTS_DIR $GITHUB_TOKEN

Publish the release; the previous step only creates a draft. Follow the link in the previous step or navigate to the GitHub releases to review the description, commit, tag, and assets before clicking "Publish"