https://python-poetry.org/docs/basic-usage/#committing-your-poetrylock-file-to-version-controlI agree at first glance it appears like poetry.lock should go in the .gitignore. However, the official docs state that in the case of developing an application (like DTS), one should commit the generated poetry.lock file to version control, as it provides a universal lock on python dependencies, across all minor versions of python specified in the pyproject.toml, and it also speeds up the dependency resolution process.
I gather from reading some posts online that some folks do opt to .gitignore their poetry.lock files for shippable applications, relying solely on the pyproject.toml as a source of truth for dependency versions. But, again this approach does not guarantee common dependencies across all the python minor versions supported by the project.
I will bring this up at the CI call tomorrow morning for feedback though.