feat: List multiple versions in latest.txt
.
#123
Merged
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.
At present, https://webterm.run/latest.txt lists only one version. The issue with that is this https://webterm.run/latest.txt starts showing the latest version as soon as the release PRs are merged, even before the release binaries are compiled and uploaded to GitHub releases.
This causes a small time window (after release PR is merged, and https://webterm.run/latest.txt shows the latest version, but before the latest version binaries are compiled and uploaded to GitHub releases) in which the install script would fail because it wouldn't be able to download the latest release.
This PR fixes this issue by listing multiple versions in https://webterm.run/latest.txt and updating the installation script to fallback to second latest version if latest version binaries are not found.
In addition, this PR also now automatically updates the frontend version to keep it in sync with crates' version.