build(deps): bump the wasmtime group across 1 directory with 2 updates - #9309

Keep all Cranelift JIT crates on the same release

When building with --features jit, crates/jit combines types and traits from cranelift, cranelift-jit, and cranelift-module, but this change upgrades the first and third to 0.136 while leaving cranelift-jit on 0.135. The lockfile consequently contains both 0.135 and 0.136 copies of core Cranelift crates, so JITModule implements the 0.135 Module trait and uses 0.135 IR types while this crate imports their incompatible 0.136 counterparts; supported JIT builds therefore no longer compile. Upgrade/migrate cranelift-jit with the other crates, or retain the 0.135 versions until that is possible.

AGENTS.md reference: AGENTS.md:L259-L263

Useful? React with 👍 / 👎.

@coderabbitai how can I manipulate .github/dependabot.yml so that this happens?

#!/bin/bash
ast-grep outline .github/dependabot.yml
sed -n '1,260p' .github/dependabot.yml

@fanninpm Your configuration already groups these dependencies in .github/dependabot.yml:

      wasmtime:
        patterns:
          - "cranelift*"
          - "wasmtime*"

The "cranelift*" pattern matches all three crates. Grouping puts available updates in one PR. It does not require all matching crates to reach the same release. Adding a separate cranelift group would not enforce that requirement.

To prevent partial automatic updates

If you want to update Cranelift manually as a coordinated set, add this entry to the Cargo section’s existing ignore list. Keep the existing ruff_* entry:

    ignore:
      # Update Cranelift manually as a coordinated set.
      - dependency-name: "cranelift*"

      # Keep the existing Ruff exclusion.
      - dependency-name: "ruff_*"

This disables routine Dependabot version updates for matching crates. It does not automate coordinated upgrades. GitHub documents ignore as the control for excluding dependencies from version updates. Dependabot documentation

To keep automatic updates

Keep the current group, but require a JIT build check before merging:

cargo check --locked --features jit

Run that check in CI with the repository’s required Rust toolchain. Grouping alone cannot replace this compatibility check.

For this PR, the configuration change would not fix the existing version mismatch. Update and migrate all three crates to a compatible release set, or restore the previous compatible versions.

_{You are interacting with an AI system.}