Skip to content

Release v1.9.3: fix doubled v in cover version badge - #64

Merged
binlecode merged 1 commit into
mainfrom
release-v1.9.3
Aug 13, 2026
Merged

binlecode merged 1 commit into
mainfrom
release-v1.9.3

Conversation

@binlecode

Copy link
Copy Markdown
Owner

The bug

The live landing page reads vv1.8.0, and a rebuild at the current tag produced vv1.9.2:

$ curl -s https://actop.pages.dev | grep -oE 'class="badge">[^<]*'
class="badge">vv1.8.0

build-cover-dist.sh substitutes {{VERSION}} with an already-prefixed v${VERSION}:

sed -i '' "s/{{VERSION}}/v${VERSION}/g" "$f"

but cover/index.html wrote v{{VERSION}} in both the hero badge and the footer — so the v was applied twice. Every publish since the placeholder was introduced has shipped the doubled prefix.

Why the template, not the output

The doubling happens at build time, so it regenerates on every publish. Editing the rendered dist-cover/ output (or the stale docs/cover.html copy) fixes one artifact and leaves the next build broken. The template has to carry a bare {{VERSION}}.

Fix

v{{VERSION}} → {{VERSION}} in both places. Verified by rebuilding: the badge now injects as v1.9.3.

Note

docs/cover.html is a stale committed copy of the rendered page — it is not the publish source (cover/index.html is, per build-cover-dist.sh's COVER_SRC default) and nothing references it. Left alone here; it should probably be deleted in a follow-up.

🤖 Generated with Claude Code

build-cover-dist.sh substitutes {{VERSION}} with an already-prefixed
v${VERSION}, but cover/index.html wrote v{{VERSION}} — so every publish
doubled the prefix in both the hero badge and the footer. The live site
reads "vv1.8.0"; a rebuild at the current tag produced "vv1.9.2".

Because the doubling happens at build time it recurs on every publish and
cannot be fixed by editing rendered output — the template itself has to
carry a bare {{VERSION}}.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@binlecode
binlecode merged commit 8feed7b into main Aug 13, 2026
5 checks passed
@binlecode
binlecode deleted the release-v1.9.3 branch August 13, 2026 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant