Change missing cache directory error to warning #24
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
Upgrade setuptools to 78.1.1 to fix path traversal vulnerability in PackageIndex.download
priya-kinthali
approved these changes
Aug 18, 2025
priyagupta108
approved these changes
Aug 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description:
This PR updates the cache lookup logic to log a warning instead of throwing an error when a cache folder path is not found on disk.
Previously: action failed with Error: Cache folder path ... doesn't exist.
Now: action logs a warning via core.warning() and continues execution.
Motivation: In many cases, missing cache simply means there are no dependencies to cache, which should not fail the workflow.
This improves developer experience by preventing unnecessary workflow failures while still surfacing useful diagnostic information.
Related issue:
#436