fix: use private clipackager cache#443
Open
christophm-pal wants to merge 1 commit into
Open
Conversation
✅ Successfully generated changelog entry!Entry generated via PR titleTo modify this entry, edit PR title using proper format. 📋Changelog Preview🐛 Fixes
|
christophm-pal
force-pushed
the
christophm/clipackager-private-cache
branch
from
July 21, 2026 12:43
4fd76cb to
b15afa4
Compare
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.
Before this PR
On Unix-based systems
cliused a shared temp-dir to cache its CLIs under predictable paths. This becomes a problem on shared instances with multiple Unix users.After this PR
==COMMIT_MSG==
Use user-based cache paths for temporary CLI cache
==COMMIT_MSG==
Possible downsides?
This change is