Skip to content

ci: no cloud caches on wavekat-ci runners - #197

Merged
wavekat-eason merged 1 commit into
mainfrom
ci/runner-caches-on-volume
Sep 13, 2026
Merged

wavekat-eason merged 1 commit into
mainfrom
ci/runner-caches-on-volume

Conversation

@wavekat-eason

@wavekat-eason wavekat-eason commented Sep 13, 2026 •

Copy link
Copy Markdown
Contributor

Why

On self-hosted runners, GitHub's cloud cache is a slow round-trip for dependency stores the runner volume already keeps warm — it can spend most of a job's timeout restoring packages that are already on disk.

What

  • docs/06-self-hosted-runners.md: new section No cloud caches on wavekat-ci, with where each cache really lives and the runner.environment == 'github-hosted' pattern for workflows that run on both.
  • CLAUDE.md: a short pointer under the runner-pool section.
  • Drop cache: npm from this repo's ci, preview, release and star-tracker workflows.

🤖 Generated with Claude Code

https://claude.ai/code/session_01USi6dgUFQi4VJZPLZ6xk44

Drop cache: npm from setup-node and document the org-wide rule: the
runner volume is the cache, and the cloud round-trip is slow.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01USi6dgUFQi4VJZPLZ6xk44
@github-actions

Copy link
Copy Markdown
Contributor

@wavekat-eason
wavekat-eason merged commit aa22dc7 into main Sep 13, 2026
4 checks passed
@wavekat-eason
wavekat-eason deleted the ci/runner-caches-on-volume branch September 13, 2026 04:53
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