[BETA-1.66] Fix wait-for-publish with sparse registry #11360
Closed
Conversation
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
rustbot
added
the
S-waiting-on-review
|
@bors r+ |
bors
added
S-waiting-on-bors
bors
added a commit
that referenced
this pull request
Nov 10, 2022
[BETA-1.66] Fix wait-for-publish with sparse registry Beta backport of #11356 r? `@epage`
|
💔 Test failed - checks-actions |
bors
added
S-waiting-on-review
|
I'm a bit confused, can you say more about why this is being backported to beta if sparse registry only works on nightly? |
|
@epage asked to backport it, but since it's nightly only, let's just close it. |
|
Yeah, my bad for late night posting :). Was thinking through sparse users being impacted but overlooked that it would only be RUSTC_BOOTSTRAP users. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Beta backport of #11356
r? @epage