Merged
Conversation
newpavlov
approved these changes
Sep 10, 2025
Member
Maybe we should consider cutting breaking releases for |
Member
Author
|
Maybe. Is there incentive for a |
Member
Author
|
I'll continue as planned for this pre-release in any case. |
Member
As I wrote in the other issue, it would allow us to rely on the MSRV-aware resolver (i.e. we will be able to bump |
Member
Author
|
@newpavlov Sounds like we have sufficient rationale to make new breaking releases of those too then. |
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 checked repo history; doesn't look like anything is missing from the CHANGELOG.
The only significant change outside the
randcrate is #1641 which is technically a breaking change torand_core, but it doesn't look like it will affect any of our implementations, so I think we're safe ignoring this discrepancy betweenmasterandrand_core v0.9.3(everything else should be using the published version anyway).Insignificant changes include #1653 which affects
rand_pcg, but I see no need for a new release of that crate.rand_distrwill require an update; lets publish arandpre-release first then updaterand_distrto use that.