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

fix: don't respect cargo-dist's install hints for curl-sh exprs #678

Merged
merged 1 commit into from
Dec 20, 2023

Conversation

Gankra
Copy link
Member

@Gankra Gankra commented Dec 19, 2023

The dist-manifest.json fundamentally lacks the information to generate perfect pretty curl-sh exprs, because it needs to be uploaded before the create-release endpoint tells us this url format. As such, oranda should ignore the manifest for these install-hints, and instead use the inference backend for them, which can use the URLs returned by the list-releases endpoint (or the github release's base url).

@Gankra
Copy link
Member Author

Gankra commented Dec 19, 2023

NB when generating Github Release Bodies cargo-dist refines the dist-manifest with the info from create-release endpoint, so even cargo-dist knows that what it uploaded is subpar.

The only way for it to upload the right thing is for create-artifact-set to return a "hint" for what the URL would be if we did make a release.

...but that still wouldn't be totally correct for an install-widget for a hypothetical Release Preview, so really we should just stop considering cargo-dist authoritative on the Best Value for these exprs.

The dist-manifest.json fundamentally lacks the information to generate perfect pretty curl-sh exprs, because it needs to be uploaded before the create-release endpoint tells us this url format. As such, oranda should ignore the manifest for these install-hints, and instead use the inference backend for them, which can use the URLs returned by the list-releases endpoint (or the github release's base url).
@shadows-withal
Copy link
Contributor

@Gankra would you say this is worthy of a patch release?

@Gankra
Copy link
Member Author

Gankra commented Dec 20, 2023

yes, I don't want axo releases to be used with the current behaviour

@Gankra Gankra merged commit b11f405 into main Dec 20, 2023
13 checks passed
@Gankra Gankra deleted the ignore-script-hints branch December 20, 2023 15:05
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.

2 participants