Skip to content

Update freeze-requirements command for parity with admin and API - #447

Merged
quis merged 3 commits into
mainfrom
install-utils-before-pip-compile
Aug 3, 2026
Merged

Update freeze-requirements command for parity with admin and API#447
quis merged 3 commits into
mainfrom
install-utils-before-pip-compile

Conversation

@quis

@quis quis commented Jul 31, 2026

Copy link
Copy Markdown
Member

See individual commits for details

quis added 3 commits July 31, 2026 15:26
We compile 2 different requirements files:
- `requirements.txt`
- `requirements_for_test.txt`

In order to know how to resolve dependencies when compiling these files
we need to look at `uv.toml`, which is copied from utils.

In order to get utils we:
1. compiled `requirements.in` into `requirements.txt`
2. installed the dependencies (including utils) from `requirements.txt`

This means that at step 1 we were using whatever version of `uv.toml`
was in the working dir. We then go on to compile
`requirements_for_test.txt` with (potentially) a different version of
`uv.toml`.

This commit makes it so that installing the specified version of utils
is the first step, before doing any compiling.
It produces a lot of output which fills the terminal.

Often I want to do `make bump-utils freeze-requirements` but have to do
a lot of scrolling back to see the useful output of `bump-utils`.

Running `uv pip sync` also produces some output about which packages
have changed, so I don’t think we need similar output from the `compile`
command.

Doing this now while I’m going through each `Makefile`.
@quis
quis merged commit eed7c50 into main Aug 3, 2026
7 checks passed
@quis
quis deleted the install-utils-before-pip-compile branch August 3, 2026 13:41
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.

2 participants