Skip to content

site: the hero has no fallback version number - #180

Merged
harshalgajjar merged 1 commit into
mainfrom
site-hero-no-stale-version
Oct 6, 2026
Merged

harshalgajjar merged 1 commit into
mainfrom
site-hero-no-stale-version

Conversation

@harshalgajjar

Copy link
Copy Markdown
Owner

Follow-up to #178, raised by Marketing. When assets/version.txt can't be read, the hero printed a hard-coded 3.0.6, a fallback that only ever goes stale.

Now there's no fallback number: if the fetch fails, the banner leaves the version out.

Checked both ways, with the file blocked in the second case:

  • file served: reminal — remote terminal · v3.16.0 · [HOST]
  • file missing: reminal — remote terminal · [HOST]

🤖 Generated with Claude Code

The hero printed VERSION = "3.0.6" whenever assets/version.txt could not
be read, a literal that only ever goes stale. With no fallback number, a
failed fetch leaves the version out of the banner instead. Checked both
ways: with the file the banner reads v3.16.0, without it the version is
simply absent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@harshalgajjar
harshalgajjar merged commit 9decdc0 into main Oct 6, 2026
3 checks passed
@harshalgajjar
harshalgajjar deleted the site-hero-no-stale-version branch October 6, 2026 04:01
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant