chore(deps): bump wit-component from 0.245.1 to 0.246.2 - #405
chore(deps): bump wit-component from 0.245.1 to 0.246.2#405dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [wit-component](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-component dependency-version: 0.246.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce9dd5a377
ℹ️ 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".
| wit-component = "0.246.2" | ||
| wit-parser = "0.245.1" |
There was a problem hiding this comment.
Updating only wit-component to 0.246.2 while leaving workspace wit-parser at 0.245.1 introduces two incompatible wit_parser crate versions in the same build. Several crates combine both APIs (for example imago-cli decodes with wit_component::decode_reader and then passes the returned Resolve/PackageId into functions typed as wit_parser::Resolve/PackageId), so this change can fail compilation with mismatched type errors even though package names are identical.
Useful? React with 👍 / 👎.
Bumps wit-component 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)