chore(deps): bump wit-parser from 0.245.1 to 0.246.2 - #415
chore(deps): bump wit-parser from 0.245.1 to 0.246.2#415dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [wit-parser](https://github.com/bytecodealliance/wasm-tools) from 0.245.1 to 0.246.2. - [Release notes](https://github.com/bytecodealliance/wasm-tools/releases) - [Commits](https://github.com/bytecodealliance/wasm-tools/commits) --- updated-dependencies: - dependency-name: wit-parser dependency-version: 0.246.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3ddeb6bef
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| webpki-roots = "1.0.6" | ||
| wit-component = "0.245.1" | ||
| wit-parser = "0.245.1" | ||
| wit-parser = "0.246.2" |
There was a problem hiding this comment.
Keep wit-parser aligned with wit-component
Bumping wit-parser to 0.246.2 while leaving wit-component at 0.245.1 splits these tightly-coupled crates across incompatible major-minor lines in 0.x semver, and this workspace uses both in the same call paths (for example, imago-cli/src/commands/update/mod.rs passes wit_parser::Resolve/PackageId into wit_component::encode). With this Cargo.toml change, Cargo resolves distinct wit_parser versions, so those types no longer match and imago-cli/runtime builds will fail with type-mismatch errors.
Useful? React with 👍 / 👎.
Bumps wit-parser from 0.245.1 to 0.246.2.
Commits
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)