fix(site): download page serves v1.0.2 — every URL verified against the published release - #552
Merged
Merged
Conversation
…he published release
The download page and vanity redirects (/download/<slug>/) were still built
from the hardcoded v1.0.0 entry: productName changed '4DA Home' -> '4DA' in
1.0.1, so every old templated asset URL 404s against current releases and the
buttons served the April build.
Regenerated site/src/_data/release.js via .claude/tmp/update_site_release.cjs
v1.0.2 --apply, which DISCOVERS asset names from the published release and
refuses ambiguity. All 6 installer URLs and sizes verified to match real
v1.0.2 assets (win 120MB, mac arm/intel 130/133MB, AppImage 201MB, deb/rpm
133MB). Two latent bugs fixed in the generator script itself (template-literal
regex escapes; single-line body capture defeated by ${base} braces) — it had
never successfully run with --apply before.
Deploy note: CF Pages 4da-site is direct-upload; this change is live only
after 'pnpm run cf:deploy' from site/ (done post-merge by the orchestrator).
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LrXvdHoDGUj99Fqf1fCYJY
runyourempire
enabled auto-merge (squash)
August 30, 2026 15:51
…nonical procedure was living in gitignored scratch
Two latent bugs fixed relative to the .claude/tmp original (template-literal
regex escapes stripped \s/\{; entry-body capture stopped at the } inside
${base} so --apply had never actually worked), plus ignore-filter entries for
updater .app.tar.gz bundles and SBOM artifacts.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01LrXvdHoDGUj99Fqf1fCYJY
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.
What
The download page and vanity redirects (/download//) were still generated from a hardcoded v1.0.0 entry in site/src/_data/release.js. productName changed
4DA Home->4DAin 1.0.1, so the templated asset names no longer exist on current releases — the buttons served the April build (or 404 shapes).How
Regenerated via
.claude/tmp/update_site_release.cjs v1.0.2 --apply— the generator discovers asset names from the published release and refuses when any installer is unmatched or ambiguous. All 6 installer URLs + sizes now match real v1.0.2 assets:Also fixed two latent bugs in the generator itself (template-literal regex escapes; entry-body capture defeated by ${base} braces) — its --apply path had never worked; its ignore-filter now excludes updater .app.tar.gz bundles and SBOM artifacts (new classes since #551).
Deploy
CF Pages
4da-siteis direct-upload (no Git integration): this is live only afterpnpm run cf:deployfrom site/ — the orchestrating session runs that immediately after this merges.Part of the 2026-08-31 audit remediation (lane E).
🤖 Generated with Claude Code
https://claude.ai/code/session_01LrXvdHoDGUj99Fqf1fCYJY