Since yesterday a lot of users in Europe found their workflows failing due to Github seemingly randomly throwing HTTP/401 on git clone/git pull when interacting with public repos without authentication.
It was now confirmed by staff member that this indeed is intentional and no further steps are planned at this point.
The service itself pulls from github to create the crates. Cargo pulls from crates.io, that is correct.
It seems that’s not the case. Crates.io only needs Github for logging in. Publishing a package uploads a .tar.gz to crates.io with the source code.
https://users.rust-lang.org/t/publishing-crates-without-github-and-some-criticism/134597/11
Who pulls from Github to create the crates? The crates are pushed by
cargo publishto crates.io’s API, not to github.crates.iodoes have an index in GitHub, but that’s legacy and pretty much unused for reads now. GitHub doesn’t store the crates themselves.