Skip to content

ci: install from the lock file with --locked - #148

Open
olivermeyer wants to merge 1 commit into
mainfrom
chore/ci-locked-installs
Open

olivermeyer wants to merge 1 commit into
mainfrom
chore/ci-locked-installs

Conversation

@olivermeyer

Copy link
Copy Markdown
Collaborator

Why?
The Supply Chain Day checklist (item 2) requires that CI installs dependencies only from the committed lock file with hashes. CI installed with uv sync --frozen, which does not check that uv.lock matches pyproject.toml, so a stale lock went unnoticed and a later uv run could re-lock.

How?
The install mise task and the nox _setup_venv helper now use uv sync --locked, so uv fails when uv.lock is out of date instead of syncing from it. The lowest-direct job resolves outside the lock on purpose and is out of scope here; https://github.com/aignostics/foundry-python/pull/533 handles it.

🤖 Generated with Claude Code

CI installed with uv sync --frozen, which skips the check that
uv.lock matches pyproject.toml. Use --locked so a stale lock fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ox-security

ox-security Bot commented Nov 6, 2026

Copy link
Copy Markdown

OX Security Logo

OX Security reviewed this pull request — nothing to fix.

✔ No issues found

Branch chore/ci-locked-installs → main

View scan in OX Security →

@codecov

codecov Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

@sonarqubecloud

sonarqubecloud Bot commented Nov 6, 2026

Copy link
Copy Markdown

@olivermeyer
olivermeyer marked this pull request as ready for review November 6, 2026 15:01
@olivermeyer
olivermeyer requested a review from a team as a code owner November 6, 2026 15:01
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.

1 participant