-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infer registry #14340
Merged
Merged
Infer registry #14340
Conversation
This file contains 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
Command-package
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
labels
Aug 1, 2024
epage
reviewed
Aug 1, 2024
epage
reviewed
Aug 1, 2024
jneem
force-pushed
the
infer-registry
branch
2 times, most recently
from
August 2, 2024 09:33
8402311
to
72411aa
Compare
epage
reviewed
Aug 2, 2024
epage
reviewed
Aug 2, 2024
epage
reviewed
Aug 2, 2024
epage
reviewed
Aug 2, 2024
epage
reviewed
Aug 2, 2024
I'm mystified by the failure in the build-std tests. When I run it locally I don't get the |
Ok, I rebased and the mysterious build-std error seems to have gone away. |
epage
reviewed
Aug 7, 2024
Infer the package registry only if all packages have the same publish field. If there is confusion, bail out instead of defaulting to crates-io.
@bors r+ |
bors
added
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
and removed
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
labels
Aug 7, 2024
☀️ Test successful - checks-actions |
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Aug 8, 2024
Update cargo 3 commits in 94977cb1fab003d45eb5bb108cb5e2fa0149672a..0d8d22f83b066503f6b2b755925197e959e58b4f 2024-08-06 21:42:10 +0000 to 2024-08-08 12:54:24 +0000 - fix: std Cargo.lock moved to `library` dir (rust-lang/cargo#14370) - fix(vendor): Strip excluded build targets (rust-lang/cargo#14367) - Infer registry (rust-lang/cargo#14340) r? ghost
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Command-package
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
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.
While working on
cargo publish
for workspaces, I noticed a few ways in which the registry inference forcargo package
seemed wrong. (This only affects the unstable-Zpackage-workspace
feature.) This is all about the interaction between--index
/--registry
, and thepackage.publish
fields.package.publish
settings, we would ignore those setting and fall back to "crates-io". After this PR, we will bail out with an error instead (unless they've specified--registry
or--index
).package.publish
settings, even if the--index
argument would have taken precedence. After this PR, we will skip registry validation in this case.package.publish
: we'd validate that it was ok, but then just not use it.