site: keep the hero release banner's version in sync automatically - #38
Merged
Conversation
The banner version was hand-edited and went stale (it still said v1.1.4 two releases later). Fill it from the same GitHub releases API fetch that resolves the APK download links; when the newest tag is ahead of the page copy, also swap the release-specific tagline for a generic 'see what's new' so an old tagline is never paired with a new version. Co-Authored-By: Claude Fable 5 <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.
The hero banner's "vX.Y.Z is live" text was hand-edited and drifted (it still said v1.1.4 two releases later). Now the version is filled from the same
releases/latestAPI fetch that already resolves the versioned APK download links:#relVersionis set to the newesttag_nameon load; no-JS/API-failure keeps the baked-in text.textContent !== tag_name), the script swaps it for a generic "see what's new" rather than pairing an old tagline with a new version. When the page copy matches the tag, the curated tagline stays.🤖 Generated with Claude Code