Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prefer fetching cargo-dist's own artifacts/metadata from axo-releases #1023

Open
Gankra opened this issue May 8, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@Gankra
Copy link
Member

Gankra commented May 8, 2024

There are several situations where cargo-dist needs to fetch itself or axoupdater:

  • in ci to bootstrap with curl-sh/irm-iex, we need to fetch the shell script, and then fetch whatever it says to fetch
  • when using the sidecar axoupdater binary, we need to fetch that (falling back to building from source)
  • when doing a selfupdate, we have to hit a releases api and fetch artifacts

This is currently a hodgepodge of fetching from github or axo releases. We should prefer axo-releases wherever possible, as the github cdn has been incredibly flakey and the api is prone to ratelimiting us.

@Gankra Gankra added the bug Something isn't working label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant