Repository navigation
chore(deps): weekly uv.lock refresh (27 packages, bub main 7b9569055) - #101
Conversation
Lockfile-only refresh from 'uv lock --upgrade' against the existing constraints. No manifest or pin changes. Notable: bub main d14de719 -> 7b9569055, anthropic 0.125.0 -> 2.6.0, pydantic-monty 1.4.0 -> 1.5.0, openai 3.42.1 -> 3.46.0, pydantic 2.14.2 -> 2.14.3, sqlalchemy 2.1.6 -> 2.1.8, cachetools 7.2.8 -> 8.0.0; distro dropped as a transitive. uv run --frozen --group test pytest: 1086 passed, 10 skipped.
There was a problem hiding this comment.
Verdict: allow — no blocking findings.
The refresh is confined to uv.lock and stays inside the existing workspace specifiers on the inspected revision 25b6c8a: uv lock --check reports the committed lock up to date, main (77f603c) is a direct parent so the diff is exactly this one commit, and the removed distro package has no remaining reference in any package's dependency list (no dangling entries).
Native Tests ran on this same checkout (25b6c8a): 1086 passed, 10 skipped in 72s. The skips are only the sandbox-integration, cargo/go-example and isolated-venv ones, so the pydantic-monty 1.4.0 → 1.5.0 bump is covered by the real run_code tests in bub-monty-env rather than mocks, and nothing in the tree imports the other majors (anthropic 2.6.0, cachetools 8.0.0, uncalled-for 0.6.0) directly.
Minor, non-blocking: the title and body say 27 packages updated, but the lock diff contains 26 version changes plus the single distro removal.
|
Landing: allow · 25b6c8a No blocking findings; the lockfile-only refresh merges cleanly into current |
Weekly
uv.lockrefresh produced by the scheduled dependency duty. Lockfile-only change:uv lock --upgradewas run in an isolated checkout ofmain(77f603c), and no manifest, constraint or pin was modified, so every resolution stays inside the existingpyproject.toml/ workspace specifiers.Requested vs actual
dependabot.yml/Renovate policy config in the repo, so this is a routine refresh rather than a security-driven manifest bump).uv.lock, +551/−550).Directly relevant to this repo's own packages:
bub(gitmain)0.6.1.dev9+gd14de719d0.6.2.dev2+g7b9569055branch = "main", unpinned by designpydantic-monty>=1.4.0(bub-monty-env) — no upper pin added or neededOther notable transitive bumps:
anthropic0.125.0 → 2.6.0,openai3.42.1 → 3.46.0,pydantic2.14.2 → 2.14.3,pydantic-core2.50.2 → 2.50.4,sqlalchemy2.1.6 → 2.1.8,typer0.27.3 → 0.28.0,cachetools7.2.8 → 8.0.0,uncalled-for0.4.1 → 0.6.0,regex2026.9.29 → 2026.11.9,authlib1.9.2 → 1.9.5,any-llm-sdk1.41.0 → 1.47.0,cyclopts5.3.2 → 5.4.0,jiter0.18.0 → 0.19.0,joserfc1.7.7 → 1.8.0,sse-starlette3.6.0 → 3.7.0,filelock4.2.6 → 4.2.9,platformdirs4.14.3 → 4.14.5,dnspython2.9.1 → 2.9.2,click8.5.0 → 8.5.1,pycryptodome4.2.0 → 4.4.0, plusruff0.17.3 → 0.17.4 (dev group).Removed transitive:
distro1.9.0 (no longer required by the updated tree).The two items worth watching are
anthropiccrossing a major boundary andpydantic-monty1.5.0, sincebub-monty-envhad to be repaired for the 1.1 → 1.4 jump in #97.Validation
uv run --frozen --group test pytest→ 1086 passed, 10 skipped (skips are environment-gated: sandbox integration, cargo/wasm and go examples, isolated-venv ablation).uv lock --checkreports the committed lock as up to date.ci.ymldispatched withnumber=101,head=25b6c8a→ run 42597790747,Testsjob success at head25b6c8a. The job log is only downloadable after the whole run (including theLanding reviewjob) finishes, so the pass counts above are from the identical local run; the nativeuv run --frozen --group test pyteststep is green.Controls preserved
No package published, no release version changed, no PR merged, no alert dismissed.
publish-request.ymlandrelease.ymlare untouched.Merge note
Draft: please treat the CI run on this branch as the acceptance signal before marking ready. Merging is not part of this change's delegated work.