Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion .github/workflows/test.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ jobs:

- uses: taiki-e/install-action@v2
with:
tool: wasmtime-cli@43.0.0
tool: wasmtime-cli@46.0.1

- uses: actions/setup-python@v5
with:
Expand Down
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,13 +74,13 @@ Be sure to run `git diff` and verify everything looks right before proceeding,
and make manual edits if necessary.

Next, commit your changes and open a PR. Once that PR is merged, tag and sign
the commit using `git tag -s v0.23.0` and push it using e.g. `git push v0.23.0`.
the commit using `git tag -s v0.23.0` and push it using `git push v0.23.0`.

Merging the PR to main will also kick off a release build, updating the `canary`
release. When that finishes, go to the [canary release
page](https://github.com/bytecodealliance/componentize-py/releases/tag/canary)
and download the `componentize_py-0.23.0-*.whl` and
`componentize_py-0.23.0.tar.gz` file, move them into a newly-created `dist`
`componentize_py-0.23.0.tar.gz` files, move them into a newly-created `dist`
directory, and run the following:

```shell
Expand Down
Loading
Loading