Skip to content

chore: update wasmtime version to 36.0.7#602

Merged
burmecia merged 1 commit into
mainfrom
bo/chore/upgarde-wasmtime
May 19, 2026
Merged

chore: update wasmtime version to 36.0.7#602
burmecia merged 1 commit into
mainfrom
bo/chore/upgarde-wasmtime

Conversation

@burmecia
Copy link
Copy Markdown
Member

@burmecia burmecia commented May 19, 2026

What kind of change does this PR introduce?

This PR is to upgrade wasmtime dependency crate version to 36.0.7, fixing dependabot alerts:

What is the current behavior?

N/A

What is the new behavior?

N/A

Additional context

N/A

Copilot AI review requested due to automatic review settings May 19, 2026 03:03
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the wasmtime dependency used by wasm_fdw to address the referenced Dependabot security advisory.

Changes:

  • Updates the wasmtime version requirement in wrappers/Cargo.toml.
  • Refreshes Cargo.lock entries for wasmtime, Cranelift, Pulley, and related transitive crates.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
wrappers/Cargo.toml Updates the wasmtime dependency requirement for wasm_fdw.
Cargo.lock Updates locked versions and checksums for wasmtime and related transitive dependencies.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@burmecia burmecia added the dependencies Pull requests that update a dependency file label May 19, 2026
@burmecia burmecia merged commit b744248 into main May 19, 2026
11 checks passed
@burmecia burmecia deleted the bo/chore/upgarde-wasmtime branch May 19, 2026 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants