goldstein/infoxtractor
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(docker): include README.md in the uv sync COPY so hatchling finds it
All checks were successful
tests / test (push) Successful in 1m22s
Details
tests / test (pull_request) Successful in 1m36s
Details

Browse source 
pyproject.toml names README.md as the readme; hatchling validates that
file exists when uv sync resolves the editable install of the project
itself. Caught on second deploy build.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Dirk Riemann 2026-04-18 12:42:29 +02:00
parent e6fcd5fc54
commit f54f0d317d
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
Dockerfile
View file

@ -46,9 +46,11 @@ RUN curl -LsSf https://astral.sh/uv/install.sh | sh \
WORKDIR /app WORKDIR /app
# Copy just the dependency manifests first so the heavy `uv sync` layer # Copy dependency manifests + README early so the heavy `uv sync` layer
# caches whenever only application code changes. # caches whenever only application code changes. README.md is required
COPY pyproject.toml uv.lock .python-version ./ # because pyproject.toml names it as the package's readme — hatchling
# validates it exists when resolving the editable install.
COPY pyproject.toml uv.lock .python-version README.md ./
# Prod + OCR extras, no dev tooling. --frozen means "must match uv.lock"; # Prod + OCR extras, no dev tooling. --frozen means "must match uv.lock";
# CI catches drift before it reaches the image. # CI catches drift before it reaches the image.