You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I would like to be able to have separate dependency caches, one for my dev dependencies, and one for my production dependencies.
Justification:
I think it could be beneficial to have a separation of dependency environment installations. For example, if my dev dependencies only install packages for linting the code like black or flake8, but my production dependencies require all of my packages for running the program. If I want to add a new linting package to my dev dependencies, it shouldn't affect my cached prod dependencies.
Hello @ahlswedes. If you use separate files for defining prod and dev dependencies I would suggest to use cache-dependency-path to specify paths for different files to generate separate cache for them. Otherwise, I would recommend to use actions/cache. According to the ADR cache logic should cover the most use cases.
Activity
dmitry-shibanov commentedon Mar 15, 2023
Hello @ahlswedes. Thank you for your report. We'll investigate the feature request.
dmitry-shibanov commentedon Jun 22, 2023
Hello @ahlswedes. If you use separate files for defining prod and dev dependencies I would suggest to use cache-dependency-path to specify paths for different files to generate separate cache for them. Otherwise, I would recommend to use actions/cache. According to the ADR cache logic should cover the most use cases.
For now I'm going to close the issue.