Repository navigation
build(deps): bump pillow to 13.0.0 with stable gradio 6.32.0 in envs/ and the validation runtime - #1620
Conversation
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.3.0...13.0.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 13.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.3.0...13.0.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 13.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.3.0...13.0.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 13.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.3.0...13.0.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 13.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.3.0...13.0.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 13.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pillow](https://github.com/python-pillow/Pillow) from 12.3.0 to 13.0.0. - [Release notes](https://github.com/python-pillow/Pillow/releases) - [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst) - [Commits](python-pillow/Pillow@12.3.0...13.0.0) --- updated-dependencies: - dependency-name: pillow dependency-version: 13.0.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
…nv/pillow-13.0.0' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…llow-13.0.0' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…r_env/pillow-13.0.0' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…ow-13.0.0' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…/pillow-13.0.0' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…/authlib-1.9.1' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…/joserfc-1.7.6' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…/filelock-4.2.1' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
…/pillow-13.0.0' into automation/dependabot-envs-2026-11-13 Co-authored-by: burtenshaw <burtenshaw@users.noreply.github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 98a563c. Configure here.
There was a problem hiding this comment.
Alignment Review Report
Automated Checks
- Lint (
usort/ruff format/ruff checkonsrc/,tests/): PASS — no issues (this PR only touchesenvs/*/uv.lock, which the lint hook doesn't cover). - Debug code (
check-debug.sh): CLEAN for this diff — the hits the hook reports (print()intest_local_docker_provider.py, docstring examples, etc.) are pre-existing insrc/openenv/core/and untouched by this PR.
Open RFCs Context
Scanned rfcs/000–014. None of the Draft/In Review RFCs (000, 001, 002, 003, 005, 006, 008, 012, 014 — In Review; 010, 011 — Draft) govern dependency/lockfile management, so there's no direct RFC overlap with this change.
Tier 1: Fixes Required
-
envs/harbor_env/uv.lock:1548,envs/helium_browser_env/uv.lock:724,envs/posttrain_env/uv.lock:921,envs/sql_optim_env/uv.lock:923,envs/tau2_env/uv.lock:1125,envs/thinkingbox_env/uv.lock:800— all six lockfiles resolvegradioto7.0.0.dev0(andgradio-clientto2.8.0.dev0), a pre-release dev build, even though each env'spyproject.tomlonly requiresgradio>=5and the latest stable release is6.32.0. These dev0 builds were only published 2026‑11‑09, so this is new to this PR (sibling envs merged earlier this week, e.g.spatial_gym_env, are still pinned to stable6.30.0). Pulling an unreleased pre-release into 6 lockfiles as a side effect of unrelated bumps (titledpillow/filelock/joserfc/authlib) looks unintentional — likely the per-env uv-lock-refresh tooling is resolving with pre-releases allowed. Recommend re-locking these 6 envs pinned to the latest stablegradio/gradio-clientinstead. -
envs/sql_optim_env/uv.lock:905andenvs/thinkingbox_env/pyproject.toml(filelock>=3.18.0, no upper bound) —filelockjumps a major version,3.32.6→4.2.1. Worth a quick check that nothing insql_optim_env/thinkingbox_envrelies on filelock 3.x behavior that changed in 4.x; CI passed, but filelock isn't exercised by most tests. - Same general note for
pillow12.3.0→13.0.0across all 6 envs — a major bump riding along with the dev0 gradio resolution. Low risk on its own (CI green), but worth re-verifying once the gradio pin above is fixed, since re-locking may change the resolved pillow/other transitive versions again.
Tier 2: Alignment Discussion
Principle Conflicts
ALIGNMENT FLAG: Pre-release (.dev0) dependency pinned into 6 production env lockfiles
- Principle/RFC at stake: PRINCIPLES.md, "What We Trade Off" → "Cutting-edge for stability: FastAPI over experimental frameworks"
- The concern:
gradio7.0.0.dev0 /gradio-client2.8.0.dev0 are unreleased pre-release builds, not the latest stable 6.x. Shipping a dev build inharbor_env,helium_browser_env,posttrain_env,sql_optim_env,tau2_env, andthinkingbox_env— all of which drive gradio-based web UIs deployed to HF Spaces — trades stability for an accidental bleeding-edge pin, the opposite of the stated trade-off. Pre-release packages can also be yanked/changed by upstream without notice, which is a worse risk profile than a stable pin. - Suggested reviewer: @Darktex (authored the "Cutting-edge for stability" principle, per
git blame), @burtenshaw (owns.github/dependabot.ymland is the co-author on all the merge commits consolidating these per-env lockfile bumps)
RFC Conflicts
None identified.
Minor note (not blocking)
.github/dependabot.yml explicitly sets exclude-paths: ["envs/**"] (added in #566, "chore: stop dependabot in envs") for the native uv ecosystem config, yet this PR consolidates a series of dependabot/uv/envs/<env>/<pkg> branches/commits authored by dependabot[bot]. This is consistent with the repeated pattern already on main (e.g. PR #1610, #1588), so it reads as an accepted, separate automation rather than a new violation — flagging only so the discrepancy between the on-disk config and the actual per-env lockfile bump source stays visible to whoever maintains that tooling.
Summary
- 3 mechanical issues to fix (pre-release gradio/gradio-client pin across 6 lockfiles; filelock major bump worth a sanity check; pillow major bump likely fine but should be re-verified after the gradio fix)
- 1 alignment point for human review (pre-release dependency vs. "cutting-edge for stability" trade-off)
- 0 RFC conflicts to discuss
Sent by Cursor Automation: Pre-review
| [[package]] | ||
| name = "gradio" | ||
| version = "6.27.0" | ||
| version = "7.0.0.dev0" |
There was a problem hiding this comment.
gradio resolves to 7.0.0.dev0 here — a pre-release dev build, not the latest stable release (6.32.0). pyproject.toml only pins gradio>=5 with no upper bound, so this looks like an unintended side effect of re-locking rather than a deliberate bump. See the top-level review for details.
| [[package]] | ||
| name = "gradio" | ||
| version = "6.29.0" | ||
| version = "7.0.0.dev0" |
There was a problem hiding this comment.
gradio resolves to 7.0.0.dev0 here — a pre-release dev build, not the latest stable release (6.32.0). Same concern as in the other 5 envs touched by this PR; see the top-level review.
| [[package]] | ||
| name = "gradio" | ||
| version = "6.30.0" | ||
| version = "7.0.0.dev0" |
There was a problem hiding this comment.
gradio resolves to 7.0.0.dev0 here — a pre-release dev build, not the latest stable release (6.32.0). Same concern as in the other 5 envs touched by this PR; see the top-level review.
| @@ -885,17 +920,18 @@ wheels = [ | |||
|
|
|||
| [[package]] | |||
| name = "gradio" | |||
| version = "6.26.0" | |||
| version = "7.0.0.dev0" | |||
There was a problem hiding this comment.
gradio resolves to 7.0.0.dev0 here — a pre-release dev build, not the latest stable release (6.32.0). Same concern as in the other 5 envs touched by this PR; see the top-level review.
| @@ -867,11 +902,11 @@ server = [ | |||
|
|
|||
| [[package]] | |||
| name = "filelock" | |||
| version = "3.32.6" | |||
| version = "4.2.1" | |||
There was a problem hiding this comment.
filelock jumps a major version, 3.32.6 → 4.2.1, riding along with the unrelated authlib/joserfc bumps in this file. Worth a quick sanity check that nothing here depends on 3.x filelock behavior.
| [[package]] | ||
| name = "gradio" | ||
| version = "6.28.0" | ||
| version = "7.0.0.dev0" |
There was a problem hiding this comment.
gradio resolves to 7.0.0.dev0 here — a pre-release dev build, not the latest stable release (6.32.0). Same concern as in the other 5 envs touched by this PR; see the top-level review.
| [[package]] | ||
| name = "gradio" | ||
| version = "6.25.0" | ||
| version = "7.0.0.dev0" |
There was a problem hiding this comment.
gradio resolves to 7.0.0.dev0 here — a pre-release dev build, not the latest stable release (6.32.0). Same concern as in the other 5 envs touched by this PR; see the top-level review.
The Dependabot bumps folded here reached pillow 13.0.0 by moving gradio to the 7.0.0.dev0 pre-release, because every stable gradio up to 6.31.0 required pillow<13. Gradio 6.32.0 allows pillow<14, so relock the six envs from main with only pillow, gradio and gradio-client allowed to move (brotli also moves in sql_optim_env). Also relock tests/validation_runtime, whose pillow bump (#1598) was reverted for the same reason. This syncs its stale openenv-core metadata with the security extra from #1506 too; uv lock --check failed on main. Locks at revision 5 were relocked with uv 0.13.7 and the others with uv 0.9.3, CI's version, so each keeps its format. uv 0.9.3 lock --check passes for all seven. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Pillow 13 no longer needs the gradio pre-release. Gradio 6.32.0, released on 12 November, allows
I also relocked The authlib, joserfc and filelock bumps folded in here already landed in #1615. Once this merges, the pillow singles (#1596, #1597, #1599, #1600, #1601, #1617) will show as merged. |
tests/validation_runtime/uv.lock conflicted with main's pillow 13 and gradio 6.32 relock (openenv#1620). Take main's lock and relock with fastmcp pinned to 4.1.2, which reproduces this branch's six package changes. Relock tests/tau2_runtime too: main's root pyproject moved on, so its openenv metadata was stale and uv lock --check failed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>



Summary
Consolidates all currently-open Dependabot PRs that touch
envs/into a single branch/PR, per the daily Dependabot-triage automation. Per policy forenvs/, these are security/dependency bumps from Dependabot and are merged as-is without additional scrutiny beyond CI passing.Folded PRs (9 total, zero merge conflicts, each individually CI-green before folding):
pillow12.3.0 → 13.0.0 inenvs/thinkingbox_envpillow12.3.0 → 13.0.0 inenvs/harbor_envpillow12.3.0 → 13.0.0 inenvs/helium_browser_envpillow12.3.0 → 13.0.0 inenvs/tau2_envpillow12.3.0 → 13.0.0 inenvs/posttrain_envauthlib1.8.0 → 1.9.1 inenvs/sql_optim_envjoserfc1.7.5 → 1.7.6 inenvs/sql_optim_envfilelock3.32.6 → 4.2.1 inenvs/sql_optim_envpillow12.3.0 → 13.0.0 inenvs/sql_optim_envDiff is exactly 6
uv.lockfiles (one per affected env), nothing else.uv lock --checkpasses cleanly in every affected env (no drift).This supersedes #1606 (
dependabot/envs-consolidated), which is nowBEHINDmain and whose folded-single list is stale (missing the 4 newsql_optim_envbumps). Please close #1606 in favor of this PR, and close the 9 individual singles listed above once this merges (this automation's tooling cannot close PRs itself).Type of Change
Alignment Checklist
.claude/docs/PRINCIPLES.mdand this PR aligns with our principles.claude/docs/INVARIANTS.mdand no invariants are violateduv lock --checkper affected environment; CI on each original single PR was green before foldingRFC Status
Test Plan
Each original single PR passed full CI (including
test-*-envsuites for the affected environments) before being folded in here. This aggregate's own CI run should be green across the board;uv lock --checkwas run locally in each of the 6 affected envs and reports no drift.Claude Code Review
N/A (automated Dependabot-triage aggregation, not a manual code change)
Note
Medium Risk
Major Pillow and coordinated Gradio upgrades across multiple runtime locks can change image/UI behavior; risk is dependency-only but wide blast radius if installs are rebuilt from these locks.
Overview
Updates six
uv.lockfiles underenvs/*andtests/validation_runtimeto refresh pinned wheels only—no application source changes.Across the affected env locks, gradio is raised to 6.32.0 and gradio-client to 2.7.2 (from several 6.27–6.30 / 2.7.0–2.7.1 combinations). Pillow is bumped from 12.3.0 to 13.0.0, including the expanded platform wheel entries typical of a major Pillow release.
In
tests/validation_runtime/uv.lock, package metadata also records the optionalsecurityextra withfastapi-guard(>=8.0.3,<9.0.0) alongside the same gradio/pillow pin updates.Reviewed by Cursor Bugbot for commit 5eee62a. Bugbot is set up for automated code reviews on this repo. Configure here.