fix(ci): regenerate consumer uv locks after the pytest 9 bump - #6134
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (3)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Railway Preview Environment
Updated at 2026-08-20T17:44:37.279Z |
Context
The api, sdk, and services unit-test jobs and the agenta-api / agenta-services image builds all fail on release/v0.112.3 because
uv sync --lockedrejects the lockfiles. Dependabot PR #5979 bumped the dev-group pytest bound inclients/python/pyproject.tomlfrom>=8,<9to>=9.0.3,<10but regenerated onlyclients/python/uv.lock. The three consumers that install agenta-client as an editable dependency embed itsrequires-devmetadata in their own lockfiles, and those still recorded the old bound, so everyuv sync --lockedsees a lock that no longer matches the source tree. In the docker builds the install step swallows the error and ships an empty venv, which the verify step then catches.Changes
Ran
uv lock(uv 0.11.14, the version CI pins) inapi/,sdks/python/, andservices/. Each lockfile changes exactly one line, in agenta-client's[package.metadata.requires-dev]block:Before:
After:
No resolved package versions change; pytest lives in the dev group, which these consumers do not install.
This clears six jobs: the api, sdk, and services unit tests, plus the agenta-api and agenta-services image builds on both amd64 and arm64. A plain re-run could not fix the image builds: the poisoned install layer sat in the shared build cache, and only a lockfile change shifts the layer digests past it.
Tests
uv lock --check(uv 0.11.14) passes in all three directories after regeneration.git diff --statconfirms 3 files, 1 line each; nothing else moved.