Attach build artifacts to GitHub releases - #501
Merged
Conversation
Pushing a version tag now builds the WASM artifacts, runs the test suite, and attaches the results to a GitHub Release: io_static.wasm, io_component.wasm, io_browser.wasm, a browser kit with the io.js loader, and a checksum file. Tags containing alpha, beta, rc, or pre are published as prereleases. The workflow can also be run by hand against an existing tag to add artifacts to older releases. Re-running it updates the release rather than failing. Also documents the release steps in DEVELOPERS.md and ignores the dist/ directory the workflow creates. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pushing a version tag now builds the WASM artifacts, runs the test suite, and attaches the results to a GitHub Release.
Until now nothing was downloadable:
browser/io_browser.wasmis gitignored and none of the 12 existing tags have artifacts, so the only way to get a working Io was to clone the repo and install wasi-sdk.What gets attached
io_static.wasmio_component.wasmwasm32-wasip2)io_browser.wasmio-browser-<tag>.tar.gzio.jsloaderSHA256SUMS.txtDetails
[0-9]*andv[0-9]*tags — all 12 existing tags match the date-based scheme.make checkbefore publishing, so a release cannot ship a failing build.alpha,beta,rc, orpreare published as prereleases.ci.yml, and uses theghCLI so no third-party actions are added.Testing
Built all three targets locally and ran the staging and notes steps verbatim from the YAML.
io_static.wasmandio_component.wasmboth execute under wasmtime, the tarball contains the expected files, and the checksum file correctly excludes itself. All five publish paths (stable, prerelease, draft, both, and re-run) were exercised against a stubbedgh.Note
The WASI 0.2 component step is
continue-on-error, so a break there degrades the release to a warning rather than blocking the other artifacts. It is the least-exercised target becauseci.ymldoes not build it. Addingmake componentto CI would be the cleaner fix and is left for a follow-up.🤖 Generated with Claude Code