Skip to content

Commit b3a2c6a

Browse files
fix : run uv lock first
1 parent 296644e commit b3a2c6a

File tree

3 files changed

+5
-1
lines changed

3 files changed

+5
-1
lines changed

backend/Dockerfile.API

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ WORKDIR /app
3030

3131
COPY pyproject.toml manage.py /app/
3232

33+
RUN uv lock
34+
3335
RUN --mount=type=cache,target=/root/.cache/uv \
3436
echo "Supplied BUILD_TARGET: $BUILD_TARGET" && \
3537
if [ "$BUILD_TARGET" = "predictor" ]; then \

backend/Dockerfile.workers

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ ENV UV_COMPILE_BYTECODE=1 \
1212
WORKDIR /app
1313

1414
COPY pyproject.toml manage.py /app/
15+
RUN uv lock
1516
RUN uv pip compile --python-version=3.10 pyproject.toml -o requirements.txt --group api --group base-workers --group ramp-workers \
1617
&& pip install --no-cache-dir -r requirements.txt
1718

docs/deployment.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ Checklist for the deployments:
1111
* Release fAIr utilities
1212
* Release fairpredictor
1313
* Verify the pypi releases for utilities and predictor
14-
* Make PR to include new versions from utilities and predictor & finally Release fAIr
14+
* Make PR to include new versions from utilities and
15+
predictor & finally Release fAIr
1516
- Document the env variable changes that are required for this release as compared to the previous version
1617

1718
Make sure you always follow this order because : new version of fAIr utilities and fAIrpredictor should be included in the fAIr backend envs, hence it can only be done after first two release . A PR would be required to bump it to new versions and docker images should be built for the prediciton and new release of fAIr should include those versions from utilties and predictor !

0 commit comments

Comments
 (0)