ci: downgrade hashbrown rather than limiting indexmap#714
Merged
XVilka merged 1 commit intopetgraph:masterfrom Jan 4, 2025
Merged
ci: downgrade hashbrown rather than limiting indexmap#714XVilka merged 1 commit intopetgraph:masterfrom
XVilka merged 1 commit intopetgraph:masterfrom
Conversation
Contributor
Author
|
Thanks for merging! Is there any plan for a point release so this can reach crates.io? |
Member
Member
|
Sure I can create a release tomorrow |
1 task
1 task
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
3 participants
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.
Pinning
indexmap = "~2.5.0"for MSRV prevents users with more current compilers from using the latest petgraph and indexmap together, even though they would otherwise work fine. Instead, dependencies can just be downgraded as needed for CI testing, and users who need the older compiler support can also manage this in their own lock files.