if you instead of doing a full re-lock went poetry lock --no-update then I expect you wouldn't get merge conflicts

@dimbleby This PR fixes the Poetry source dependency itself—it's not about any project.

@NeilGirdhar I don't know what you think I wrote but you are talking past it

this merge request currently has merge conflicts, I expect those would be avoided if poetry.lock had been updated by poetry lock --no-update

Oh, sorry, I misunderstood your comment.

Rebased with poetry lock --no-update.

My expectation was that any change to pyproject would change content-hash and so conflicts were inevitable. Such is life with lock files...

My expectation was that any change to pyproject would change content-hash and so conflicts were inevitable. Such is life with lock files...

That's correct. Can you please re-lock (--no-update) with the latest poetry version (1.7.1)? (If the lockfile does not change just change the hash and do again.)

That's correct. Can you please re-lock (--no-update) with the latest poetry version (1.7.1)? (If the lockfile does not change just change the hash and do again.)

Done. The content is as-before, with a different version in the comment. 🤷

Done. The content is as-before, with a different version in the comment. 🤷

That's fine. We just want to make sure, we always use the latest version in the project.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.