You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/0000-source_replacement_ambiguity.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ There are multiple issues that this RFC attempts to resolve around source-replac
16
16
* When Cargo is performing an API operation, source replacement is only respected for `crates-io`, not alternative registries. This is inconsistent.
17
17
* The [error message](https://github.com/rust-lang/cargo/issues/6722) for attempting to publish to a replaced crates-io is confusing, and there is no workaround other than temporarily removing the source replacement configuration.
18
18
* When performing an API operation other than `publish` with a replaced `crates-io` source, the `crates-io` credentials are sent to the replacement registry's API. This is a security risk.
19
-
* It's unclear which credentials should be used when fetching a source-replaced authenticated alternate registry (RFC 3139).
19
+
* It's unclear which credentials should be used when fetching a source-replaced authenticated alternate registry ([RFC 3139][3139]).
@@ -35,7 +35,7 @@ A repository has a local `.cargo/config.toml` that vendors all dependencies from
35
35
If the user decides to publish the crate, `cargo publish --registry crates-io` will ignore the source-replacement and publish to crates.io.
36
36
37
37
### `crates-io` mirror registry
38
-
A server has been set up that provides a complete mirror of crates.io. The user has configured a `~/.cargo/config.toml` that points to the mirror registry in the `[registries]` table. The mirror requires authentication to access (based on RFC 3139).
38
+
A server has been set up that provides a complete mirror of crates.io. The user has configured a `~/.cargo/config.toml` that points to the mirror registry in the `[registries]` table. The mirror requires authentication to access (based on [RFC 3139][3139]).
39
39
40
40
The user can log in to the mirror using `cargo login --registry mirror`. Fetching and building use the mirror.
41
41
@@ -123,4 +123,6 @@ Cargo's tests rely on the ability to replace the crates.io source and have the c
0 commit comments