-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): bump hashbrown to v0.14.5 #1721
Conversation
773eeae
to
5bcdb84
Compare
Sorry about the force pushes, I committed my suggestion instead of closing it. Looks like hashbrown team doesn't want to fix this and Tokio pinned it in their CI and readme. We can do the same for this PR. Let me know if you want me to push a commit with those changes. |
5bcdb84
to
eba1dd0
Compare
Pushed! Looks like the only feature needed is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason getting errors with hashbrown pinned to 0.15.0 for MSRV 1.63.0, also reproducible locally:
|
034e4e0
to
f9cf1cd
Compare
I force pushed a commit to only bump hashbrown to |
f9cf1cd
to
6d93c91
Compare
No, I believe you simply need to enable So
works for me. |
6d93c91
to
52fa540
Compare
@tnull thanks for testing it out, I pushed your suggestion and CI passing so all good. Just FYI the only default feature not included is: allocator-api2: Enables support for allocators that support allocator-api2. |
Thanks for updating and testing this guys! Is there anything else needed here, or is this good to merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 52fa540
@tvolk131 I was just giving anyone else interested a chance to comment, but looks good to me so I'll merge it. Thanks for the suggestion to do this version bump. |
Bump
hashbrown
to v0.15I ran
cargo build-all-features
andcargo test-all-features
locally for thecore
crate with no issues. Here's the output for the former:The relevant changelog can be found between here and here
The only notable breaking change I found was that the MSRV was bumped to v1.63. However, this is the same MSRV as we already use, so it's not a breaking change for us.