fix: clear package manager cache during update to ensure fresh downloads (v4.3.10) #19
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
…ads (v4.3.10) Resolves issue where 'ccs update' would report success but serve cached package versions, requiring manual 'npm cache clean --force'. Changes: - Node.js (bin/ccs.js): Added cache clearing for npm, yarn, pnpm before update - Bash (lib/ccs): Added 'npm cache clean --force' before npm update - PowerShell (lib/ccs.ps1): Added 'npm cache clean --force' before npm update - Updated manual fallback commands to include cache clearing - Non-blocking: continues with update even if cache clearing fails Version bumped to 4.3.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
ccs updatewas reporting success but serving cached package versions from npm, requiring users to manually runnpm cache clean --forceto get the latest version.Solution
Automatically clear package manager cache before updating in all three implementations:
npm cache clean --forceyarn cache cleanpnpm store pruneChanges
Testing
Impact
Users no longer need to manually clear cache before updating.
ccs updatenow guarantees fresh downloads from the registry.