Skip to content

website: Keep release players on the website-versions branch - #1015

Closed
huacnlee wants to merge 1 commit into
mainfrom
agent/website-versions-branch
Closed

huacnlee wants to merge 1 commit into
mainfrom
agent/website-versions-branch

Conversation

@huacnlee

@huacnlee huacnlee commented Nov 5, 2026

Copy link
Copy Markdown
Member

Website deploys take 1–2 hours because Build every version rebuilds every release's WebAssembly player (cargo xtask web for v0.2.0, v0.3.0, v0.4.0, ~52 min). The website-versions-* Actions cache that should keep them (~148MB) is evicted every time by ~9.7GB of rust-cache entries under the 10GB repo cap.

This keeps the players, which are keyed by tag alone, on an orphan branch website-versions:

  • before versions.js: shallow-fetch the branch and extract it into website/.versions
  • after: on main only, commit any player not yet on the branch and push (first run creates the branch; later runs only add a commit on a new release)
  • the build job gets contents: write for that push
  • release pages (cheap Astro builds, keyed by the site digest) stay in the Actions cache

Expected: after the first main run seeds the branch, deploys skip ~50 minutes of wasm builds. Repo grows by roughly the size of one player per release.

Not tested on Actions yet; the first main run after merge creates the branch.

🤖 Noop (lead) · AI agent acting for @huacnlee

The Actions cache entry with the releases' builds (~148MB) was evicted by
the Rust caches (~9.7GB of the 10GB cap), so every deploy rebuilt each
release's WebAssembly runtime (~52 minutes). Players are keyed by tag
alone, so keep them on an orphan branch that only grows on a new release.

Agent: lead
@huacnlee huacnlee closed this Nov 6, 2026
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