Skip to content

install dev group explicitly in setup_env#748

Open
Benjamin-Knight wants to merge 1 commit into
dbt-msft:masterfrom
Benjamin-Knight:fix/devcontainer-dev-group
Open

install dev group explicitly in setup_env#748
Benjamin-Knight wants to merge 1 commit into
dbt-msft:masterfrom
Benjamin-Knight:fix/devcontainer-dev-group

Conversation

@Benjamin-Knight

@Benjamin-Knight Benjamin-Knight commented Jul 16, 2026

Copy link
Copy Markdown
Collaborator

What

Install the dev dependency group explicitly during devcontainer setup instead of relying on uv's implicit default-group behaviour. resolve #747

Changes

  • uv sync --all-extras → uv sync --all-extras --group dev
  • Run pre-commit install via uv run so it uses the synced environment
  • Added a comment explaining why the group is named explicitly

Why

uv's default-group behaviour varies by version, so --all-extras alone didn't reliably install the dev group. Naming it explicitly makes the devcontainer deterministic across uv versions, ensuring pre-commit, pytest, and other dev tooling are always available.

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) <noreply@anthropic.com>
@Benjamin-Knight Benjamin-Knight changed the title fix(devcontainer): install dev group explicitly in setup_env install dev group explicitly in setup_env Jul 16, 2026
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.

Devcontainer setup doesn't reliably install the dev dependency group

1 participant