Enable cargo:token as a global-credential-provider #140
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
qsantos
changed the title
qsantos
force-pushed
the
cargo-registry-auth
branch
from
cc0bfc2
to
3e6d0bd
Compare
NiklasRosenstein
requested changes
Dec 13, 2023
added 2 commits
December 13, 2023 15:57
Since 1.74, Cargo requires a credential provider to be set up to download crates from private registries. This changes set the cargo:token credential provider. This stays compatible with the mitmproxy credentials injection. This will also be useful when switching to cargo-based authentication instead of relying on credentials injection.
qsantos
force-pushed
the
cargo-registry-auth
branch
from
3e6d0bd
to
ba6a567
Compare
NiklasRosenstein
approved these changes
Dec 13, 2023
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.
Enable cargo:token as a global-credential-provider
Since 1.74, Cargo requires a credential provider to be set up to download crates from private registries. This changes set the cargo:token credential provider. This stays compatible with the mitmproxy credentials injection.
This will also be useful when switching to cargo-based authentication instead of relying on credentials injection.