chore(deps): update rust crate bincode to v2 #844
No reviewers
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital!844
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/bincode-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.3→2.0Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
1f5fe9246254b9c2a01c54b9c2a01ce5e723351eiced_beaconto the bincode 2 APIRenovate bumped the workspace dependency to bincode 2.0, but the only consumer of it, the `iced_beacon` crate in the `orbital-iced` submodule, still used the bincode 1.x API, so the workspace no longer compiled. The migration lives in the submodule, so point at `orbital-iced` `master`, which now contains it. That also picks up the sha2 0.11 digest fix and the submodule's own Renovate configuration. `bincode = { version = "2.0", features = ["serde"] }` is now explicit. It happened to work before only because `cargo-hot-protocol` enables the same feature in the same build, and cargo unifies them.0a528f199d279911980b