Repository navigation
chore(deps): commit poetry.lock for reproducible dev builds (#59) - #60
Merged
Merged
Conversation
The repo used Poetry without a committed lock, so every `poetry install` resolved "latest in range" at install time — letting the tandem development branches drift onto different dependency trees. This pins an exact tree. Generated with `poetry lock` (Poetry 2.3.1). Pins: views-pipeline-core 2.3.0, views-frames 1.6.0, + full transitive tree (4803 lines). `poetry check --lock` consistent. Note: development's pyproject currently pins views-pipeline-core via the PyPI range ">=2.1.3,<3.0.0" (resolved → 2.3.0) — the git-source / 3.0.0 change the issue's rationale references has not landed on development yet. Re-run `poetry lock` to refresh the pin when it does. Closes #59. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #59.
What
Generates and commits
poetry.lock(was missing — the.gitignoreonly carries the commented-out#poetry.locktemplate line, so nothing was ignoring it; a lock was simply never generated).Why
Without a committed lock, every
poetry installresolves "latest in range" at install time, letting the tandemdevelopmentbranches drift onto different dependency trees. The lock pins an exact, reproducible tree.Pins
views-pipeline-core2.3.0views-frames1.6.0poetry lockvia Poetry 2.3.1;poetry check --lockconsistent.The issue references development "now sourcing views-pipeline-core from its development branch over git (3.0.0)" — but development's
pyproject.tomlcurrently still pins the PyPI range>=2.1.3,<3.0.0(resolved → 2.3.0). That git-source change has not landed on development yet. This lock pins the current tree; re-runpoetry lockto refresh when the git/3.0.0 source lands (the issue's second checkbox).🤖 Generated with Claude Code