From 653af1039c995956eefd88e0dde59b6d6ca1bdcd Mon Sep 17 00:00:00 2001 From: Ben Knight Date: Thu, 16 Jul 2026 12:28:34 +0000 Subject: [PATCH] fix(devcontainer): install dev group explicitly in setup_env The setup script relied on uv installing the `dev` dependency group by default. That behaviour varies by uv version, so on a fresh devcontainer build the `dev` group (which provides pre-commit) was not installed and `pre-commit install` failed with `command not found`. Restore the explicit `--group dev` that was dropped in b9a4b8b, and run pre-commit via `uv run` so it no longer depends on the venv being active. Co-Authored-By: Claude Opus 4.8 (1M context) --- .devcontainer/setup_env.sh | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/.devcontainer/setup_env.sh b/.devcontainer/setup_env.sh index e1f68bea..9d6a493f 100644 --- a/.devcontainer/setup_env.sh +++ b/.devcontainer/setup_env.sh @@ -21,6 +21,8 @@ command -v uv >/dev/null 2>&1 || pip install uv [ -d .venv ] || uv venv source .venv/bin/activate -# Install both backend extras so the devcontainer can exercise either connection path. -uv sync --all-extras -pre-commit install +# Install both backend extras so the devcontainer can exercise either connection path, +# plus the dev dependency group (pre-commit, pytest, etc.). Groups are installed +# explicitly rather than relying on uv's default-group behaviour, which varies by version. +uv sync --all-extras --group dev +uv run pre-commit install