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
GitHub's workflow schema
workflow-v1.0.json is GitHub's schema for workflow files, copied unchanged from
actions/languageservices, file
workflow-parser/src/workflow-v1.0.json, at commit
4043eda158e16579cc5fb1b0b07a4bce2a76f0b5 (5 August 2026). It is MIT licensed;
LICENSE is that repository's licence, copied from the same commit.
g1t does not read it at run time. src/syntax.rs lists the keys each part of a
workflow may have, and its tests check those lists against this file, so they
cannot drift from GitHub's. To update it, copy the file again, write the commit
here, and run cargo test -p g1t-actions.