Closed dominik-bln closed 5 years ago
Here is what happens in our CI pipeline:
Renovate should definitely detect and update the poetry.lock, I'll mark this as a bug
It looks like you have poetry.lock
file in a subdirectory of the repository, so I managed to reproduce it by placing poetry.lock
in a subdirectory. It should be easy to fix then.
Yes, our lock file is in a subfolder.
Thanks for your quick responses and the great tool.
:tada: This issue has been resolved in version 16.6.3 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
We're still seeing this issue, with poetry.lock
in the repository root. Renovate commits only modify the pyproject.toml
and leave the lock file untouched.
(Using renovate 17.3).
@kadrach please raise a separate bug report with full details and logs
What Renovate type are you using?
Renovate CLI via renovate/renovate Docker image in Gitlab-CI
Describe the bug
We updated the docker image of our renovate bot from 14.x to 16.x yesterday. Since then it automatically started updating our
pyproject.toml
file, but ignores thepoetry.lock
.Did you see anything helpful in debug logs?
Not really, but here is the relevant output:
To Reproduce
pyproject.toml:
poetry.lock:
Expected behavior
The
poetry.lock
file is updated alongside thepyproject.toml
. Renovating Poetry is documented.Screenshots