ci(desktop): rebuild site after stable release so version follows#4036
Merged
Conversation
The marketing site bakes the version at build time from R2 latest.json, and pages.yml only rebuilds on site/** pushes — so a release left the static value (and JSON-LD softwareVersion) lagging until the next site edit. site.js's runtime .rxv refresh fixes the live page but not first paint / SEO. Dispatch pages.yml from the mirror job's stable path, once R2 latest/ has actually moved.
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.
Why
The marketing site resolves the displayed version from R2's
latest.jsonin two layers: a build-time bake in
index.astroand a runtime refresh insite.jsthat rewrites every.rxvspan on page load. The runtime layerkeeps the live page current, but
pages.ymlonly rebuilds onsite/**pushes — so after a release the baked value (and the JSON-LD
softwareVersionused for SEO) lagged behind until an unrelated site edittriggered a rebuild. First paint briefly showed the old version.
What
Dispatch
pages.ymlfrom the desktop release'smirrorjob, right after astable release has actually moved R2
latest/(skipped for canary and rc,which don't move
latest/). The job gets a scopedactions: writefor thedispatch. No new secrets.
This pairs with the R2 CORS fix that lets the runtime
.rxvrefresh reachdl.reasonix.iofromreasonix.io; together the site now follows everyrelease with no manual edit.