chore: pin all dependency versions in requirements.txt #24
Labels
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/paper-dynasty-card-creation#24
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Unpinned dependencies can silently introduce breaking changes when Docker images are rebuilt. This caused a production outage in the Major Domo project when an unpinned FastAPI upgrade changed redirect behavior.
Task
requirements.txtfor any unpinned or floor-constrained dependencies==)Why This Matters
Every Docker build should produce an identical image. Unpinned deps mean a
git revertdoesn't actually roll back to the previous working state — you get the old code with new libraries.Fixed in PR #32: #32
Pinned the two unpinned packages —
peewee==3.19.0andpolars==1.36.1. All other 50 dependencies were already on exact==pins.