the landing page stops naming a version it cannot keep up with

A number beside the button is a promise to rebuild the site on every
release, and the site had already broken it once -- v2.12.19 sat there
for 30 hours after v3.0.1 shipped. Removing the label is cheaper than
keeping it honest: the button says what it does, latest/ decides which
bytes, and nothing on the page can drift out of date.

The stamping code and the runtime label refresh go with it. The manifest
is still fetched -- /get/ bakes it for the picker, and the count note
still compares the catalogue against what the release publishes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: function-store

website/README.md

@@ -206,17 +206,22 @@ resolve pinned URLs from the manifest, because reproducible installs are
 what make bug reports correlatable (`publish.py`, "Never publish a mutable
 `latest/<Package>.tox`").
 
-Only the visible version **label** is stamped at build time, read from the
-rolling manifest at
-`https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/manifest.json`.
-A stale label is cosmetic: it sits next to a download that is still
-correct. Rebuild after a release if you want the number to match.
-
-The page also tries to refresh label and hrefs at runtime, but **that fetch
-is currently blocked**: neither the r2.dev bucket nor
-`storage.functionstr.com` sends an `Access-Control-Allow-Origin` header.
-Enabling CORS on the bucket would make the label self-correcting and would
-upgrade the hrefs from `latest/` to the pinned release in the browser.
+**The landing page carries no version number at all** — the buttons say
+"Get FNSTools", not "Get FNSTools v3.0.1". Nothing release-shaped is
+stamped into it, so there is no number that can go stale and no reason to
+rebuild the site when a release ships.
+
+`/get/` bakes the published manifest (it carries the `rails` hashes), but
+that is display data: the paste script it hands you re-fetches the rolling
+manifest *at paste time* from inside TouchDesigner via `requests`, and
+resolves every artifact and hash from that. A `/get/` page built months ago
+still installs the current release; only the picker's package list can lag.
+
+The page also tries to refresh hrefs at runtime, but **that fetch is
+blocked**: neither the r2.dev bucket nor `storage.functionstr.com` sends an
+`Access-Control-Allow-Origin` header. Enabling CORS would let the browser
+upgrade hrefs from `latest/` to the pinned release, and would keep the
+picker's list current between deploys.
 
 The bootstrap artifact is `FNSTools.tox`, renamed from
 `FunctionStore_tools_2025.tox` in the v3.0.0 redesign. The filename is a

website/index.html

@@ -349,7 +349,7 @@
       <a href="#credits">Credits</a>
       <a href="https://patreon.com/function_store" target="_blank" rel="noopener">Patreon</a>
       <a class="btn btn-secondary" href="https://github.com/function-store/FunctionStore_tools" target="_blank" rel="noopener">GitHub</a>
-      <a class="btn btn-primary js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Get FNSTools<span class="js-fns-ver">v3.0.1</span> →</a>
+      <a class="btn btn-primary js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Get FNSTools →</a>
     </nav>
   </div>
 </header>
@@ -364,7 +364,7 @@ <h1 class="hero-title">TouchDesigner,<br />minus the busywork.</h1>
       Take the whole toolkit or pick the three tools you actually want.
     </p>
     <div class="hero-cta">
-      <a class="btn btn-primary btn-lg js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Get FNSTools<span class="js-fns-ver">v3.0.1</span> →</a>
+      <a class="btn btn-primary btn-lg js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Get FNSTools →</a>
       <a class="btn btn-secondary btn-lg" href="/docs/">Read the docs</a>
     </div>
     <ul class="hero-meta">
@@ -402,7 +402,7 @@ <h3>Drop one <code>.tox</code></h3>
           arrives empty — it carries the installer, the updater and nothing else yet.
           The container you drop <em>is</em> the install target.
         </p>
-        <a class="btn btn-primary js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Download<span class="js-fns-ver">v3.0.1</span></a>
+        <a class="btn btn-primary js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Download</a>
         <p class="path-note">Already have a toolkit container? Grab the <a class="js-fns-installer" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNS_Installer.tox" download>bare installer</a> instead (~14 KB).</p>
         <p class="path-note">No download at all: <a href="/get/">pick your tools online</a> and paste one line into the Textport — it fetches and verifies everything itself.</p>
       </div>
@@ -861,7 +861,7 @@ <h2 style="font-size: clamp(28px, 3.6vw, 36px); font-weight: 700; letter-spacing
       One <code>.tox</code>, then pick what you need. It is free, and it takes about a minute.
     </p>
     <div class="hero-cta">
-      <a class="btn btn-primary btn-lg js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Get FNSTools<span class="js-fns-ver">v3.0.1</span> →</a>
+      <a class="btn btn-primary btn-lg js-fns-download" href="https://pub-8001b4bd92174be7a4544571b53f23da.r2.dev/fnstools/latest/FNSTools.tox" download>Get FNSTools →</a>
       <a class="btn btn-secondary btn-lg" href="/docs/">Read the docs</a>
     </div>
   </div>
@@ -918,7 +918,6 @@ <h2 style="font-size: clamp(28px, 3.6vw, 36px); font-weight: 700; letter-spacing
         setAll('.js-fns-installer', function (a) {
           a.href = base + '/' + m.release + '/' + INSTALLER;
         });
-        setAll('.js-fns-ver', function (s) { s.textContent = ' ' + m.release; });
         if (m.packages && m.packages.length) {
           setAll('.js-fns-count', function (s) {
             s.textContent = String(m.packages.length);

website/tools/build-site.mjs

@@ -416,17 +416,14 @@ ${items}
       </div>`;
 }).filter(Boolean).join('\n');
 
-// The published release, stamped into the version LABEL at build time.
+// The published release. NOTHING release-shaped is stamped into the landing
+// page any more: the download hrefs point at the mutable latest/ aliases,
+// and the version text next to them is gone. A release therefore cannot
+// leave this page stale, and does not need a rebuild to stay correct.
 //
-// The hrefs themselves are no longer stamped: they point at the mutable
-// latest/ aliases, so a release cannot leave them serving stale bytes even
-// if nobody rebuilds. Only the visible "v3.0.1" text is stamped, and it is
-// cosmetic — a stale label sits next to a download that is still correct.
-//
-// The page also refreshes both at runtime, but that fetch cannot be relied
-// on: neither the r2.dev bucket nor storage.functionstr.com serves an
-// Access-Control-Allow-Origin header, so the browser blocks it. Enabling
-// CORS on the bucket is what would make the label self-correcting too.
+// Still fetched because /get/ bakes the published manifest (it carries the
+// `rails` hashes the paste script shows), and because the count note below
+// compares the catalogue against what the release actually publishes.
 async function publishedRelease() {
   // CI sets this. Without it the stamped release depends on what is published
   // at the moment the build runs, so a release cut between commit and CI would
@@ -465,20 +462,15 @@ if (fs.existsSync(landing)) {
     `$1${pages.length}$2`);
 
   if (live) {
-    // Only the label. The hrefs stay on latest/ -- see publishedRelease().
-    // No leading space: the span sits inside a .btn, which is inline-flex
-    // with its own 8px gap, so one would render as a double space.
-    out = out.replace(/(<span class="js-fns-ver">)[^<]*(<\/span>)/g,
-      `$1${live.release}$2`);
-    console.log(`stamped label ${live.release} (${live.packages?.length ?? '?'} packages published)`);
+    console.log(`release ${live.release} published (${live.packages?.length ?? '?'} packages)`);
     if (live.packages && live.packages.length !== pages.length) {
       console.log(`note: catalog has ${pages.length} packages but ${live.release} publishes ` +
         `${live.packages.length} — the site lists the catalog, so these align at the next publish`);
     }
   } else if (process.env.FNSTOOLS_NO_RELEASE_FETCH) {
-    console.log('release fetch skipped — version label keeps whatever index.html already says');
+    console.log('release fetch skipped — landing page carries no release, so nothing to keep');
   } else {
-    console.log('note: could not reach the release manifest — version label keeps whatever index.html already says');
+    console.log('note: could not reach the release manifest — /get/ falls back to the repo manifest');
   }
   fs.writeFileSync(landing, out);
 } else {