fix(site): Windows installer pickup + light-mode god-rays + stale-cache bypass#182
Merged
Merged
Conversation
- God rays now render in light mode too: a transparent (premultiplied-alpha) canvas lets the warm-paper page show through the gaps, and a uLight-adapted shader draws deeper, softer shafts on paper while keeping the dark-mode glow unchanged - Pick up the release's Windows *-setup.exe from the resolved asset list: the Get Started and hero download buttons light up and link to the installer when one exists, and stay an inert 'coming soon' chip otherwise - Disable the cursor-reflection coat interaction for now (gated behind a flag, code left in place)
A deploy fired minutes after a publish could resolve a release whose just-attached assets (notably the Windows *-setup.exe) were missing from a CDN-cached releases/latest body — the runner's region kept serving a stale response well past its 60s s-maxage. The page then shipped a 'coming soon' Windows chip for a build that actually exists. Force revalidation with no-cache headers + a per-build cache-buster query param so the build always sees current release state.
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.
Lands the Windows installer pickup on the landing page (plus god-rays in light mode), and a build-time fix so the resolver can't ship a stale "coming soon" for a Windows build that already exists.
Why
After v0.4.35 published with a real Windows
*-setup.exe, the live page still showed Windows as "coming soon". Root cause: the assets-based download logic — which lights up and links the setup.exe when the release ships one — only existed on this branch;mainnever had it. So every deploy frommainrendered the inert chip regardless of the release.Changes
design(site)(269c9b0): Pick up the release's Windows*-setup.exefrom the resolved asset list — the Get Started + hero download buttons light up and link to the installer when one exists, else stay an inert "coming soon" chip. God rays now also render in light mode (transparent premultiplied-alpha canvas + light-adapted shader; dark mode unchanged). Cursor-reflection coat gated off behind a flag for now.fix(site)(e46840b): Bypass the CDN-cachedreleases/latestat build time (no-cache headers + per-build cache-buster query param). A deploy fired minutes after a publish could otherwise resolve a stale release body missing the just-attached setup.exe — exactly the failure seen on the v0.4.35 release.Validation
Local build against the live API resolves the v0.4.35 setup.exe link (32067-byte index.html) + the DMG + updates manifest stable
0.4.35.