Claudeagent and Claudeagent`actions/cache`, `actions/cache/restore` and `actions/cache/save` are the real actions now, at the version a step names, as `setup-node` and every other action are: g1t's runner no longer stands in for them by name. They save to and restore from the repository's cache through the toolkit's cache service, which g1t already answered, so an entry `actions/cache` saves is restored by `setup-node` with the same key and paths, and the other way round, as on GitHub. Entries the stand-in saved were versioned its own way and are not restored by the real action: each cache misses once, then fills again. As for every toolkit cache, an entry between 100 and 128 MB, which the toolkit sends in one request, is not saved. The Actions guide and the limitations say so.fdde3acHistory
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.