Repository navigation
fix: resolve devs junobuild-* versions from crates.io - #98
Closed
peterpeterparker wants to merge 1 commit into
Closed
peterpeterparker wants to merge 1 commit into
peterpeterparker wants to merge 1 commit into
Conversation
Contributor
Author
|
Claude / AI bullshit. |
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
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.
I think because we use the juno main repo to build which itself patches crates.io (see https://github.com/junobuild/juno/blob/main/Cargo.toml), the actions always built the latest version (since I always release from there). We should remove the patch this way the pinned version devs use is used.