Skip to content

Add dev docs on how to deal with the wasi-sdk shasums #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zkat wants to merge 1 commit into from
Open

Add dev docs on how to deal with the wasi-sdk shasums #102

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,4 +20,20 @@ releases. New releases are a three-step process:

From here, just wait for the [release
action](https://github.com/fastly/compute-sdk-cpp/actions/workflows/release.yml)
to complete, and you'll have a live release!
to complete, and you'll have a live release!

## Updating `wasi-sdk` shasums

Whenever we update the version of `wasi-sdk` we release with, we need to update
[`wasi-sdk-shasums.txt`](./wasi-sdk-shasums.txt) to have the right shasums and
filenames, as well as updating our workflow to use the new version. To do so:

1. Go to [the release workflow](./.github/workflows/release.yml) and update the
`WASI_SDK_VERSION` env var to the new version.
1. Go to the `Assets` section in the relevant release under
https://github.com/WebAssembly/wasi-sdk/releases.
1. Update `wasi-sdk-shasums.txt` with the filenames and shasums from this
section, removing the `sha256:` prefix from each shasum.

Everything should checksum during release now. You can check this by downloading
all the relevant tarballs and running `sha256sum -c wasi-sdk-shasums.txt`
Loading