chore(deps): bump wasmtime from 42.0.1 to 43.0.2 - #74
Merged
Conversation
Bumps [wasmtime](https://github.com/bytecodealliance/wasmtime) from 42.0.1 to 43.0.2. - [Release notes](https://github.com/bytecodealliance/wasmtime/releases) - [Changelog](https://github.com/bytecodealliance/wasmtime/blob/v43.0.2/RELEASES.md) - [Commits](bytecodealliance/wasmtime@v42.0.1...v43.0.2) --- updated-dependencies: - dependency-name: wasmtime dependency-version: 43.0.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Brian Krabach (bkrabach)
added a commit
that referenced
this pull request
May 18, 2026
* fix(deps): align wasmtime-wasi to v43 to match wasmtime The wasmtime crate was bumped to v43 (via dependabot PR #74) but wasmtime-wasi remained pinned at v42, pulling two incompatible wasmtime versions into the dependency graph: error[E0308]: mismatched types --> crates/amplifier-core/src/bridges/wasm_tool.rs:66:43 | 66 | wasmtime_wasi::p2::add_to_linker_sync(&mut linker)?; | ---------------------------------- ^^^^^^^^^^^ expected | `&mut Linker<_>`, found `&mut Linker<WasmState>` | note: there are multiple different versions of crate `wasmtime` in the dependency graph This broke Rust Core CI on every PR (and silently on main, since the workflow only triggers on PRs targeting main). Fix: bump wasmtime-wasi to v43, aligning with the wasmtime crate. Both now resolve to 43.0.2. Verified locally with all four CI commands from .github/workflows/rust-core-ci.yml: - cargo check -p amplifier-core --features wasm ✓ - cargo check -p amplifier-core -p amplifier-core-py ✓ - cargo test -p amplifier-core --no-run ✓ - cargo fmt -p amplifier-core -p amplifier-core-py --check ✓ - cargo clippy -p amplifier-core -p amplifier-core-py -- -D warnings ✓ Co-authored-by: Amplifier <amplifier@microsoft.com> * chore: bump version to 1.5.3 Patch bump for the wasmtime-wasi alignment fix. Triggers PyPI wheel publication via Build Wheels workflow when v1.5.3 tag is pushed. Co-authored-by: Amplifier <amplifier@microsoft.com> * chore: bump __version__ in python/amplifier_core/__init__.py to 1.5.3 Missed this version stamp in the previous bump commit. The Python package's runtime __version__ must match pyproject.toml and the Cargo crate versions, or installed builds report stale version. Co-authored-by: Amplifier <amplifier@microsoft.com> --------- Co-authored-by: Amplifier <amplifier@microsoft.com>
Brian Krabach (bkrabach)
added a commit
that referenced
this pull request
May 18, 2026
The workflow was only triggered on pull_request and push to rust-core. This meant when main went red — as happened after IT's wasmtime auto-fix in #74 — there was no signal until the next PR opened. Add 'main' to the push branches so any direct push (merge, admin push, revert) triggers a full CI run on the new HEAD. Catches future regressions immediately. Co-authored-by: Amplifier <amplifier@microsoft.com>
Brian Krabach (bkrabach)
added a commit
that referenced
this pull request
May 19, 2026
* ci: run Rust Core CI on push to main, not just PRs The workflow was only triggered on pull_request and push to rust-core. This meant when main went red — as happened after IT's wasmtime auto-fix in #74 — there was no signal until the next PR opened. Add 'main' to the push branches so any direct push (merge, admin push, revert) triggers a full CI run on the new HEAD. Catches future regressions immediately. Co-authored-by: Amplifier <amplifier@microsoft.com> * chore(ci): bump GitHub Actions to Node 24-compatible versions - actions/checkout: v4 → v6 (v6.0.2 latest; Node 24 since v5) - actions/setup-python: v5 → v6 (v6.2.0 latest; Node 24 dep upgrade) - actions/upload-artifact: v4 → v7 (v7.0.1 latest; Node 24 since v6) - actions/download-artifact v4 → v8 (v8.0.1 latest; Node 24 since v7) - PyO3/maturin-action: v1 unchanged (already runs on node24) No FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 env var needed — every action used in this workflow is already on Node 24 after this bump. Resolves GitHub's Node 20 deprecation deadline of 2026-06-02. --------- Co-authored-by: Amplifier <amplifier@microsoft.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
1 participant
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.
Bumps wasmtime from 42.0.1 to 43.0.2.
Release notes
Sourced from wasmtime's releases.
... (truncated)
Changelog
Sourced from wasmtime's changelog.
... (truncated)
Commits
f8557c1Release Wasmtime 43.0.2 (#13240)efe2dc0Fix panicking overflow when calculating table sizes (#13243)cd4b6edRelease Wasmtime 43.0.1 (#13001)96dde3a[43.0.x] Combined backports for a 43.0.1 release (#13005)be23469Release Wasmtime 43.0.0 (#12806)d225583cm-async: Fix cancelling a completed host task (#12797) (#12801)b0dc282[43.0.0] A few more backports (#12795)51ec9dbWASIP3 update to latest rc (#12781) (#12786)e7e3996[43.0.0] Add release notes (#12770)4b24669[43.0.0] Backport fixes, refactorings, and updates to wasip3 limits (#12769)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.