Skip to content

inspect-swe: lower inspect_ai floor 0.3.249 → 0.3.233#31

Open
gas2own wants to merge 1 commit into
mainfrom
lower-inspect-ai-floor-0.3.233
Open

inspect-swe: lower inspect_ai floor 0.3.249 → 0.3.233#31
gas2own wants to merge 1 commit into
mainfrom
lower-inspect-ai-floor-0.3.233

Conversation

@gas2own

@gas2own gas2own commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

What

Lower the solvers/inspect-swe inspect_ai floor from >=0.3.249 to >=0.3.233 in both dependencies and [tool.uv].override-dependencies, regenerate the frozen uv.lock, and correct the misattributing comment.

Why

0.3.233 is the tightest floor that carries both fixes this arm needs:

Fix First landed
Bridged-tool list[ContentText] result serialization (#3879) 0.3.220
Accept inline role: "system" from bridged Anthropic clients (commit 8829d740 / #4095) — folds into ChatMessageSystem instead of raising RuntimeError: Unexpected message role: system 0.3.233

The previous >=0.3.249 floor over-specified: the old comment attributed the system-role fix to 0.3.249, but it actually landed at 0.3.233. The 0.3.249 changelog (Moonshot provider, inspect ctl control-channel changes, an OpenAI with_raw_response bridge fix) contains nothing this arm requires. inspect_swe==0.2.66 itself declares inspect-ai with no floor, so nothing transitive forces 0.3.249.

Beyond being unnecessary, >=0.3.249 is actively harmful: when astabench is overlaid via --with and pins inspect_ai==0.3.233 (allenai/asta-bench#156), a >=0.3.249 override conflicts and blocks the resolver from landing the intended 0.3.233. Lowering the floor removes the conflict.

Lock

uv lock regenerated — the base project still resolves inspect_ai 0.3.249 (newest satisfying the floor, no astabench group active); the runtime downgrade to 0.3.233 happens when the astabench overlay re-resolves. Only the override/specifier metadata lines changed.

Coordination

Paired with allenai/asta-bench#156 (astabench pin ==0.3.203==0.3.233). Neither alone lands 0.3.233 at runtime — the astabench pin sets the exact version, this floor stops over-constraining it. Tracking + full analysis: allenai/gas2own#346.

🤖 Generated with Claude Code

0.3.233 is the tightest floor carrying both fixes this arm needs:
  - 0.3.220: bridged-tool list[ContentText] result serialization (#3879)
  - 0.3.233: accept inline role="system" from bridged Anthropic clients
             (commit 8829d740 / #4095) — folds into ChatMessageSystem
             instead of raising 'Unexpected message role: system'

The previous >=0.3.249 floor over-specified: its justifying comment
misattributed the system-role fix to 0.3.249, but that fix landed at
0.3.233. Nothing the inspect-swe / claude_code Anthropic-bridge arm needs
lives above 0.3.233. More importantly, a >=0.3.249 override conflicts with
astabench's exact pin when astabench is overlaid via --with, blocking the
resolver from landing 0.3.233. Lowering the floor (dependencies +
override-dependencies) lets the coordinated astabench==0.3.233 pin
(allenai/asta-bench#156) resolve. Lock regenerated; base project still
resolves 0.3.249, the astabench overlay re-resolves to 0.3.233 at runtime.

Ref allenai/gas2own#346.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@gas2own
gas2own marked this pull request as draft July 23, 2026 23:04
@gas2own

gas2own commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Draft — paired with allenai/asta-bench#156, which is blocked: astabench also depends on agent-eval[leaderboard]==0.1.51inspect-ai==0.3.203, so the solve overlay can't resolve to 0.3.233 until agent-eval relaxes its pin. This floor change is still correct and necessary, but not sufficient on its own. See allenai/gas2own#346.

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