Repository navigation
Conversation
rami3l
marked this pull request as ready for review
October 30, 2026 14:47
ChrisDenton
approved these changes
Oct 30, 2026
djc
approved these changes
Oct 30, 2026
rami3l
added
the
backport
rami3l
force-pushed
the
backport/solaris-file-locking
branch
from
October 31, 2026 08:34
b8628a7 to
e307b04
Compare
rami3l
force-pushed
the
backport/solaris-file-locking
branch
from
October 31, 2026 08:59
e307b04 to
a9c0c9d
Compare
Member
Author
@djc Yeah I've done just that. Should be better now? |
Contributor
|
Better, yes, but why not do the semver-compatible dependency updates? |
Member
Author
@djc I also did just that in In fact, from my side |
This branch has not been deployed
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.
Related to #5166.
@rust-lang/rustup If there are no remaining concerns regarding this new dot release, I think we start the process shortly after this PR is merged. Otherwise, please feel free to raise them in the aforementioned issue.