Skip to content

ci: set cache-mode on release workflows - #378

Draft
claude[bot] wants to merge 1 commit into
mainfrom
ci/cache-mode
Draft

ci: set cache-mode on release workflows#378
claude[bot] wants to merge 1 commit into
mainfrom
ci/cache-mode

Conversation

@claude

@claude claude Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Requested by David Sanders · Slack thread

Before: The release workflow inherits GitHub Actions' default cache access, so the release job (and the test.yml jobs it calls via uses:) can restore and save Actions caches during a release run; today only the release job's own setup-node step opts out with package-manager-cache: false.

After: cache-mode: none at the top of release.yml disables cache restore and save for every job in the release run, including the reusable test jobs, regardless of per-step settings. A denied cache step logs a message and continues; the job does not fail.

This adopts GitHub's new cache-mode key (changelog, syntax reference) so the release path never depends on Actions cache contents.

How: one top-level cache-mode: none line (with a short comment) added to .github/workflows/release.yml. PR CI does not exercise the release workflow, so the first release after merge is the real test.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MYe3WCXtgiqomNuVQdi4Yd


Generated by Claude Code

Add top-level `cache-mode: none` to release.yml so release runs never
read from or write to the Actions cache, regardless of per-step
settings.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MYe3WCXtgiqomNuVQdi4Yd
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