Hi @daveisfera, thanks for the contribution!

Since we auto-enabled caching when a packageManager field is present in PR #1348, we’ve seen a number of regressions, particularly with Yarn and pnpm. Those issues led us to intentionally limit auto-caching to npm only in PR #1374.

To avoid landing in the same spot again, we’re holding off on changes that expand automatic package manager detection beyond the current npm-only behavior. If you have any further concerns, please don’t hesitate to reach out, and we appreciate your feedback and suggestions for future enhancements.