In #150, I described a usecase were caching the Poetry installation was causing the dependency cache step to break when the .lock was updated.
In summary, if some action used a cached poetry install (skips running snok/install-poetry), the configurations set in with would not be done, which caused any new dependency installs to not be cached, as Poetry by default installs venvs not in the .venv path (so the cache step can't find the .venv directory to cache).
This PR adds a section in the docs to clarify this and guide users to a fix.
In #150, I described a usecase were caching the Poetry installation was causing the dependency cache step to break when the
.lock
was updated.In summary, if some action used a cached poetry install (skips running
snok/install-poetry
), the configurations set inwith
would not be done, which caused any new dependency installs to not be cached, as Poetry by default installs venvs not in the.venv
path (so the cache step can't find the.venv
directory to cache).This PR adds a section in the docs to clarify this and guide users to a fix.