chore: pin exact version of heapless
#171
Closed
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
For the moment the `heapless` crate is locked on 0.7.0, because 0.8.0 still requires some work (the revert happened with jamesmunns#164). The problem is that the "0.7.0" version requirement also matches "0.8.0", so for the moment we need "~0.7.0" to not allow a minor version update (which would brake the package). Signed-off-by: Gabriel Goller <[email protected]>
✅ Deploy Preview for cute-starship-2d9c9b canceled.
|
|
Can you clarify what you think this changes? As far as I am aware, with how cargo resolves semver versions, When the major version is |
|
You're right, this was an error on my local registry, my bad! |
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.
For the moment the
heaplesscrate is locked on 0.7.0, because 0.8.0 still requires some work (the revert happened with #164). The problem is that the "0.7.0" version requirement also matches "0.8.0", so for the moment we need "~0.7.0" to not allow a minor version update (which would brake the package).