Skip to content

chore: work around crates.io 403 by injecting User-Agent into fetchcrate - #489

Closed
stackptr wants to merge 1 commit into
mainfrom
chore-fix-fetchcrate-user-agent
Closed

stackptr wants to merge 1 commit into
mainfrom
chore-fix-fetchcrate-user-agent

Conversation

@stackptr

Copy link
Copy Markdown
Owner

crates.io now returns HTTP 403 for requests from bare curl User-Agents
under their API data access policy. nixpkgs fetchcrate sends no
User-Agent, breaking any Rust package that fetches crates at build time
(e.g. deploy-rs). This overlay wraps fetchcrate to inject a cargo-style
User-Agent until nixpkgs fixes it upstream.

Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com

crates.io now returns HTTP 403 for requests from bare curl User-Agents
under their API data access policy. nixpkgs fetchcrate sends no
User-Agent, breaking any Rust package that fetches crates at build time
(e.g. deploy-rs). This overlay wraps fetchcrate to inject a cargo-style
User-Agent until nixpkgs fixes it upstream.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Copy link
Copy Markdown
Owner Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@stackptr

Copy link
Copy Markdown
Owner Author

Closing in favour of building from the local host instead of GHA, which avoids the crates.io User-Agent restriction entirely.

@stackptr stackptr closed this May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant