Skip to content

backend: use fully-resolved pip-compile deps#3310

Open
mistydemeo wants to merge 2 commits into
mainfrom
misty/pip-compile
Open

backend: use fully-resolved pip-compile deps#3310
mistydemeo wants to merge 2 commits into
mainfrom
misty/pip-compile

Conversation

@mistydemeo

Copy link
Copy Markdown
Contributor

This is a potential alternative to #3305. That one swapped us to a pyproject.toml with uv's lockfile format, while this is a lighterweight change that keeps our dependencies specified as-is while adding pip-compile format fully-resolved files. I've swapped the old dependency specifications to .in files and used the .txt files for the fully-resolved versions.

This should be compatible with both dependabot and renovate if we decide to adopt those.

@socket-security

socket-security Bot commented May 13, 2026

Copy link
Copy Markdown

No dependency changes detected. Learn more about Socket for GitHub.

👍 No dependency changes detected in pull request

@mistydemeo mistydemeo force-pushed the misty/pip-compile branch 2 times, most recently from 640ce17 to 98d8ea8 Compare May 13, 2026 21:13
@mistydemeo mistydemeo force-pushed the misty/pip-compile branch from 98d8ea8 to f02b434 Compare May 21, 2026 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant