syntaqxEvery npm install in g1t's workflows starts from npm's downloads for the whole lockfile, rather than from Wrangler's alone. All of them restored and saved one key, npm-Linux-<lockfile hash>, and the first job to finish on main (Deploy's check, which installs only the root) saved its 73 MB under it; a key is written once, so every later job restored those 73 MB and downloaded the rest of its install through the runner's egress, where downloads were breaking off. The key is now npm-full-, and only jobs that install the whole lockfile save it: CI's TypeScript and Build jobs, and the desktop release's Linux builds. Every job that installs part of it (Deploy's check, migrate and stages, the mobile, CLI and desktop publish jobs, the runner release) only restores. On main, Deploy's new npm-cache job keeps it: it looks the key up without downloading, and when this lockfile has none it starts from the last lockfile's, downloads every package with scripts off and saves them; nothing waits for it, and a failed download leaves the cache as it was and the run green. A test holds every workflow to one npm key and to saving it only from whole installs.427d96bHistory
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml