From 44d1387007dd99995018377f4a8c16cee44e0540 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 13 Aug 2026 14:44:58 +0000 Subject: [PATCH] Ignore uv.lock: a test-run byproduct, not a consumed lock file Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01731mKtVzsfeT4Vi3TvkR48 --- .gitignore | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.gitignore b/.gitignore index 9a94144..eac96f3 100644 --- a/.gitignore +++ b/.gitignore @@ -98,10 +98,9 @@ ipython_config.py # Pipfile.lock # UV -# Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control. -# This is especially recommended for binary packages to ensure reproducibility, and is more -# commonly ignored for libraries. -# uv.lock +# Deployment installs via `pip install .` (Dockerfile), so no lock file is consumed +# anywhere; a uv.lock is just a byproduct of running the test suite through `uv run`. +uv.lock # poetry # Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.