Commit a poetry.lock for reproducible dev builds
This repo uses Poetry but does not commit a poetry.lock. The standard Python
.gitignore here only carries the commented-out #poetry.lock template line (with
a note recommending you commit it), so nothing is actively ignoring it — a lock was
simply never generated/committed.
This matters more now: development was just changed to source views-pipeline-core
from its development branch over git (the unreleased 3.0.0, pending PyPI). Without
a committed lock, every poetry install resolves "whatever is latest on that moving
branch at install time" — so the tandem development branches can silently drift onto
different pipeline-core commits and dependency trees. A lock pins an exact commit + tree.
To do
Reference (does it right): views-platform/views-hydranet — Poetry with a committed poetry.lock.
Follow-up to the pipeline-core 3.0.0 git-source change on development.
Commit a
poetry.lockfor reproducible dev buildsThis repo uses Poetry but does not commit a
poetry.lock. The standard Python.gitignorehere only carries the commented-out#poetry.locktemplate line (witha note recommending you commit it), so nothing is actively ignoring it — a lock was
simply never generated/committed.
This matters more now:
developmentwas just changed to sourceviews-pipeline-corefrom its
developmentbranch over git (the unreleased 3.0.0, pending PyPI). Withouta committed lock, every
poetry installresolves "whatever is latest on that movingbranch at install time" — so the tandem
developmentbranches can silently drift ontodifferent pipeline-core commits and dependency trees. A lock pins an exact commit + tree.
To do
poetry lockand commit the resultingpoetry.lock.developmentadvances (poetry lock).Reference (does it right):
views-platform/views-hydranet— Poetry with a committedpoetry.lock.Follow-up to the pipeline-core 3.0.0 git-source change on
development.