Repository navigation
Update the crate lock to almide v0.67.0 - #11
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
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
1 participant
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.
Moves the committed
crate/Cargo.lockfrom almide 0.66.0 (5e3cc64fc) to the v0.67.0 release commit, main e2cb6c3b4. almide and almide-mir are pinned at the same rev, and the wasm-tools family moves from 0.259 to 0.261, following almide.The deploy already builds this rev: the
compiler-updateddispatch run 38010884240 (2026-10-10 00:52) runscargo update almideand succeeded on e2cb6c3b4. This PR makes the committed lock agree with what is deployed.