Update dependencies to fix issue consuming - #69
Merged
Merged
Conversation
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against ce8a585 |
skeet70
approved these changes
Sep 16, 2026
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
3 participants
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.
Because the test fixtures were locked to the tag
v0.32.0, even when uniffi 0.32.1 was released, this crate would stay on 0.32.0. This caused an issue consuming the latest version of the crate from ironcore-alloy because v0.32.0 -> v0.32.1 bumpedtoml, and our version of the dependency must stay compatible with uniffi-bindgen's.The fix applied here is to instead depend on the
release-v0.32.xtag, which will get bumped when new patches are released.Other dependency bumps are also to match uniffi's (but afaik they aren't required to match like toml is)