rust-lang / rust-lang/hashbrown
`hashbrown` 0.15.1 bumped the MSRV on a patch release
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 358
- Avg merge
- 11h 57m
- Merged PRs (30d)
- 2
Description
We are users of hashbrown, directly as well as through other dependencies over which are out of our control (notably, indexmap). Unfortunately, yanking hashbrown 0.15.0 and releasing 0.15.1 also bumped the MSRV in that patch release, which renders it incompatible with our MSRV of 1.63.
As some of our dependencies had already upgraded to 0.15 (and hence require 0.15.x as a minimum version), we can't simply pin hashbrown back to a compliant MSRV. I'd therefore like to ask whether you could reconsider bumping the MSRV on a patch release. And, if really necessary, at least make it a minor release or at least a separate patch release so that we have options left.
Thank you, it would be highly appreciated!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the hashbrown 0.15.0 and 0.15.1 release history and the project's MSRV policy. Determine whether the patch release's MSRV change should be reconsidered, and document the decision and any resulting release-policy or versioning changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100