Repository navigation
fix(ci): drop restore-keys on Claude Code npm cache so pin bumps install - #1169
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Since the 2026-10-05
aeon-updatesync bumped the Claude Code pin to 2.1.287, every skill run on aeon-agent and miroshark-aeon failed at "Install Claude Code":There was no cache under
claude-code-Linux-2.1.287, sorestore-keysrestored the oldclaude-code-Linux-2.1.168cache from July. Its cached packument lists versions only up to 2.1.168, andnpm install --prefer-offlinetrusts that stale metadata, so npm reports that 2.1.287 does not exist. The install fails, no new cache key is ever saved, and every later run fails the same way.Fix
Remove the
restore-keysfallback from the Claude Code npm cache inaeon.ymlandmessages.yml. An exact-key hit still installs offline. A miss (first run after a bump) downloads fresh and saves the new key. The old tarball never helped a bump anyway, since each release ships new binaries.The broken instances were unblocked by deleting their stale
claude-code-Linux-2.1.168caches. This PR stops it from happening again on the next bump.