shadowdaoandClaude Sonnet 5 76b2942db1 ci: bump the OBS deps cache key -- it was stuck on a permanently bad entry ...

actions/cache never overwrites an existing key: once a key has a saved
entry, later jobs' save steps are always skipped as a no-op regardless
of cache hit/miss. The very first job to ever populate this cache did
so before the "Drop non-relocatable OBS build tree" cleanup step
existed, so that entry included the bad, path-baked build_x86
directory -- and every run since has kept restoring that same bad
entry, not self-healing after "one more transitional run" the way it
looked when this was last checked. Confirmed live: a run just now hit
the identical stale-path CMakeCache.txt error against the same
original job hash (f72837d12c75c64a) from hours ago.

Bumping the key (obs-deps- -> obs-deps-v2-) is what actually forces a
fresh save under the cleanup step's watch, since the key content
(buildspec files) hasn't changed and nothing else would invalidate it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RL8abRmgFXkVASHkkqiJbE

2026-09-07 10:47:56 -07:00

..

build.yml

ci: bump the OBS deps cache key -- it was stuck on a permanently bad entry

2026-09-07 10:47:56 -07:00

release.yml

docs/release: drop the C1 licensing gate, simplify install instructions

2026-09-07 09:40:49 -07:00