Repository navigation
Release 5.11.2 - #289
Merged
Merged
Release 5.11.2#289
Conversation
Putting the version requirement at 0.2.191 breaks compatibility with crates that set a requirement of <0.2.190 (like quiche). Cargo doesn't allow excluding specific versions, so the next best thing we can do is switch back to our old version requirement now that `libc 0.2.191` exists. While this does allow a known-incompatible version, cargo won't select it unless someone explicitly asks for it. Meanwhile allowing lower versions makes foundations compatible with repos that need to stick to versions <0.2.190 for other reasons, such as compatibility with `nix` (which has not released a libc 0.2.191-compatible version yet.)
fisherdarling
approved these changes
Oct 26, 2026
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.
Fixed