fix: bump vf + fix lock - #3187
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…onfig Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
mikasenghaas
marked this pull request as ready for review
August 4, 2026 01:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
uv.lockto fix the lockfile drift onmain: the research-environments bump raised the workspace envs'verifiersfloor (>=0.2.2.dev65→>=0.2.2.dev73) without updating the lockfile, souv sync --lockedfails in CI. Most of the lock diff is uv 0.12.1 normalizing dependency markers; CI resolves the same uv version.deps/verifierssubmodule to latest main (d30a3f48e, 0.2.2.dev76) and raise theverifiersfloors inpyproject.tomlandpackages/prime-rl-configsto>=0.2.2.dev76.ServingConfig→ServeConfiginprime_rl.configs.orchestrator, following the upstream rename (vf#2237). This fixes the Slim install job on main, which resolvesverifiersfrom PyPI (already on the renamed API) and failed withmodule 'verifiers.v1' has no attribute 'ServingConfig'.Verification
uv lock --checkonmain(78cef28) fails withThe lockfile at uv.lock needs to be updated, and the Slim install job fails on theServingConfigimport — the two CI failures on main.uv lock --checkanduv sync --all-extras --all-packages --lockedpass; the slim wheel installed in an isolated venv (pulling verifiers 0.2.2.dev76 from PyPI) imports all five config entrypoints;tests/unit/orchestratorpasses (97 passed, 1 known box-local qwen3-vl flake tracked in fix: token_id-formatted logprob tokens in the qwen3-vl fake engine #3161).🤖 Generated with Claude Code
Note
Low Risk
Dependency floor bump and a straight rename to match verifiers’ API; no behavioral logic changes in orchestrator beyond the config class name.
Overview
Raises the
verifiersfloor to>=0.2.2.dev76in the root andprime-rl-configspackages so locked installs and PyPI-based slim builds resolve the same release.Aligns orchestrator config with upstream vf#2237 by renaming
ServingConfigtoServeConfigand subclassingvf.ServeConfig;EnvConfig.serveuses the new type. Docstrings are updated to match the renamed “serve” block.Reviewed by Cursor Bugbot for commit 7a4801f. Bugbot is set up for automated code reviews on this repo. Configure here.