Repository navigation
Look up the latest release in the install commands - #66
Merged
Merged
Conversation
The manual install commands now ask GitHub for the latest release instead of naming a version, so a release no longer needs a README change afterwards. The lookup uses curl alone, since the checksum path is for people without gh.
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
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 manual install commands ask GitHub which release is the latest (the
/releases/latestredirect) instead of naming a version, so a release no longer needs a README PR afterwards. The lookup usescurlalone, because the checksum path is for people withoutgh. SettingVERSIONby hand still works for a specific tag.I ran the snippet in zsh and bash, as far as the checksum check: both resolved v0.17.0 and verified the archive. The release example in the Releasing section is now a fixed
v1.2.3.