chore: update many dependencies #50
Merged
+1,065
−810
Conversation
This file contains 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
SupernaviX
commented
Feb 21, 2025
| thiserror = "1.0.64" | ||
| wasmtime = { version = "23.0.1" } | ||
| thiserror = "2.0.11" | ||
| wasmtime = { version = "28.0.1" } |
There was a problem hiding this comment.
Wasmtime version 29 (the major version after this) stops using async_trait in generated bindings, which involves actual code changes to resolve. I didn't include it in this PR.
SupernaviX
commented
Feb 21, 2025
| async-trait = "0.1.83" | ||
| utxorpc = { version = "0.8.0" } | ||
| utxorpc = { version = "0.10.0" } |
There was a problem hiding this comment.
The newer version of the utxorpc crate comes with a newer utxorpc-spec (which includes governance parameters). This changes the Block type passed to handle_chain. so sickos like me who call handle_chain directly also need to upgrade to this utxorpc version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tested on my machine. These package updates are harmless and don't include relevant breaking changes.
Some of these older versions are flagged by
cargo audit, some are shared by the service itself (and having multiple versions bloats the build), and some I just bumped because why not.