docs: point the macOS download at /releases, not /releases/latest#271
Merged
Conversation
GitHub's /releases/latest skips pre-releases, and the desktop builds are
published as pre-releases (unsigned, no notarization). So the "latest"
redirect resolves to connector-v0.1.28 — the connector, not the desktop app:
$ curl -o /dev/null -w '%{redirect_url}' .../releases/latest
https://github.com/ElePerson/Cheers/releases/tag/connector-v0.1.28
Every download entry added in #267 pointed there. Send them to the releases
list instead, and say which tag to pick, since that page interleaves
connector-v* and desktop-v* builds.
The connector install snippets in website/connector*.html keep using
/releases/latest/download/… — the connector releases are not pre-releases,
so that redirect resolves correctly for them.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #267 — the download links it added resolve to the wrong release.
The bug
GitHub's
/releases/latestskips pre-releases, and the desktop builds are published as pre-releases (unsigned, not notarized — seerelease-desktop.yml). So the redirect lands on the connector:Every "Download for macOS" entry added in #267 pointed there — a user clicking the freshly-promoted download button in the README header or the landing-page hero would have landed on a connector release with no
.dmgin sight.The fix
Point them at the releases list (
/releases) and say which tag to pick, since that page interleavesconnector-v*anddesktop-v*builds:README.md/README.zh-CN.md— "Get Cheers" table row and the native-clients section.website/index.html/index.zh-CN.html— hero CTA button and the macOS card in#clients.Left alone on purpose: the connector install snippets in
website/connector*.htmluse/releases/latest/download/…. Connector releases are not pre-releases, so that redirect resolves correctly for them.Verification
Rendered both landing pages locally: no
a[href*="releases/latest"]remains, both download links resolve to/releases, the macOS card grew by one line without breaking the 2×2 grid (rows stay equal-height at 304/280 px, no horizontal overflow).Context
This surfaced while tagging
desktop-v0.1.1, which is now published with the four desktop fixes thatdesktop-v0.1.0was missing.🤖 Generated with Claude Code