Use fetch-cargo-vendor v2#62
Merged
Merged
Conversation
The v2 fetcher uses a custom user-agent that doesn’t trigger crates.io rate limits so easily.
Contributor
|
Thanks! Pushed a change to only use v2 if it exists, since it's planned to be removed in the next staging cycle: NixOS/nixpkgs#501979 |
CathalMullan
approved these changes
Jun 12, 2026
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
2 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.
The vendor fetching is hitting 403s from crates.io, which causes extensions to get removed. Using the v2 script from NixOS/nixpkgs#512735 should make the fetcher more reliable.