fix(cache): disable setup-bun cache to avoid 5-retry HTML-error burn (#1580)

The upstream oven-sh/setup-bun action saves with a deterministic key
(Bun version) that isn't ref-aware. On every second-and-subsequent run
against the same PR ref, the GitHub cache API rejects the duplicate
key+ref with a 409 (HTML body), and @actions/cache treats the unparsable
response as transient and burns ~20-30s on 5 retries before warning.

The 35 MB Bun binary downloads in 2-3s, so disabling the cache is a net
wallclock win and removes the noisy warning that fires on every PR push
after the first.

Closes #1252

Co-authored-by: Mukunda Rao Katta <mukunda.vjcs6@gmail.com>
This commit is contained in:
necofuryai
2026-08-07 07:57:18 -07:00
committed by GitHub
co-authored by Mukunda Rao Katta
parent c4190dbd78
commit 4c4309a064
2 changed files with 10 additions and 0 deletions
+8
View File
@@ -193,6 +193,14 @@ runs:
with:
bun-version: 1.3.14
token: ${{ inputs.github_token || github.token }}
# Disable setup-bun's cache. The upstream save step uses a deterministic
# key (Bun version) and isn't ref-aware: on every second-and-subsequent
# run against the same PR ref the GitHub cache API rejects the duplicate
# key+ref with a 409 (HTML body), and @actions/cache treats the unparsable
# response as transient and burns ~20-30s on 5 retries before warning.
# The 35 MB Bun binary downloads in 2-3s, so disabling the cache is a net
# wallclock win and removes the noisy warning. See issue #1252.
no-cache: true
- name: Setup Custom Bun Path
if: inputs.path_to_bun_executable != ''