chore: pin all Python dependency versions in requirements.txt #82
Labels
No Label
ai-changes-requested
ai-failed
ai-pr-opened
ai-reviewed
ai-reviewing
ai-working
ai-working
bug
enhancement
feature
in-queue
performance
security
tech-debt
todo
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/paper-dynasty-discord#82
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==)requirements-dev.txtif not already doneWhy 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.Opened PR #83: #83
Approach: Sourced exact versions from the live production container (
pip freeze), pinned all 12 deps with==, movedpytest/pytest-asyncioto a newrequirements-dev.txt, and pinned the Dockerfile base image topython:3.12.13-slim.