Repository navigation
[3574 by Claude Opus 5.5] Bump two coding-agent CLIs to their latest stable versions (from the 2026-11-15 "Update coding agents and models" report). Follow the same touch list as #3527 (the previous bump PR): Dockerfile pins, AGENT_DEFAULTS, version/types.ts, the root... - #3575
integry merged 1 commit into
Conversation
![propr-dev[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
….8 to 1.5.9, following the same touch list as #3527. Codex, Mistral Vibe and the model catalog are unchanged. Every suite I ran passed, including the runtime tool-policy test against the real 2.1.325 binary with nothing skipped. Checks against the real releases - Antigravity 1.5.9: the installer `manifests/linux_amd64.json` lists release `4515810895593472` with the SHA-512 from the issue. I downloaded the tarball: the checksum matches, it holds one `antigravity` entry, and `--version` prints `1.5.9`. The offline `agy changelog` lists no model changes. It does confirm the new `run_workflow` tool, which hands work to subagents from a Python script. - Claude Code 2.1.325: the `latest` dist-tag is 2.1.325 and `stable` is still 2.1.311. I compared the bundled model catalogs of the 2.1.323 and 2.1.325 binaries: they are identical. That means the `native_1m` set in `reviewContextBudget.ts` only needed its version comment updated. - Permission and sandbox changes don't affect ProPR: - Every Claude run passes `--dangerously-skip-permissions` (`dockerArgsBuilder.ts:176`, `claudeHelpers.ts:271`). - Analysis runs also pass `--setting-sources ''`, so the new rule about `.claude/settings.local.json` allow rules in containers doesn't matter. - Nothing in ProPR turns on Claude Code's sandbox or uses scheduled tasks or `/loop`. What changed - Version pins: `Dockerfile.agent` (both stages, plus Antigravity's release ID and SHA-512), `scripts/build-images.sh`, `scripts/verify-antigravity-image.sh`, `AGENT_DEFAULTS` in `modelDefinitions.ts`, and `version/types.ts`. - Root package files: `package.json` now asks for `^2.1.325`. The `package-lock.json` diff touches only the claude-code package and its 8 platform packages. - License listing: `THIRD_PARTY_LICENSES.md`. The bundled license text is identical to 2.1.323's. - Tests: `modelDefinitions`, `versionService`, `nativeLogPolicy`, `reviewContextBudget` and `releaseImageFixtures`. The verifier fixture is renamed from `antigravity-verifier-pinned-1.5.8.json` to `-1.5.9.json`. - Docs: the CHANGELOG entry, `managed-diagnostics.md`, `native-provider-log-policy.md` and `pr-commands.md`. I also added a short paragraph about `run_workflow` to `agents-and-models.md`. Test results | Suite | Result | |---|---| | `test/agentToolPolicyRuntime.test.ts` (real 2.1.325, and Codex 0.168.0, both on PATH from `/tmp`) | 11/11 passed, 0 skipped | | modelDefinitions, reviewContextBudget, releaseImageFixtures, antigravityAgent, core versionService, nativeLogPolicy | 6/6 files passed | | thirdPartyNotices, agentDockerfileSupplyChain, agentVersionManagement, agentRegistryManagedAgentPin, agentBundleContentFiles | 5/5 files passed | Changing the root lockfile doesn't require regenerating any checksums: this repo pins no lockfile checksums and has no qualification `SHA256SUMS`, which live in propr-routing. For the PR description - Watch item, not a blocker: Antigravity 1.5.9 gives all users the `run_workflow` tool. On large headless tasks this may raise token use and run time. `-p`, `--print-timeout` and exit codes are unchanged. - The Claude Code catalog also includes `claude-mythos-5-2`, which `reviewContextBudget.ts` doesn't list. It was already in 2.1.323, isn't in ProPR's catalog, and the issue rules out catalog changes, so I left it alone. This change has no visible UI, so there are no previews.
|
/review |
|
✅ AI Code Review Complete requested by @integry Posted 1 review: |
🔍 AI Code Review — codex:gpt-6-astraOverall EvaluationReady to merge within the visible scope. The PR consistently updates Claude Code to 2.1.325 and Antigravity to 1.5.9 without introducing unrelated implementation changes. ✅ Consistent version updates — Docker stages and labels, build-script defaults, both application version maps, and Claude’s lockfile entries agree on the new versions. ✅ Release safeguards preserved — Antigravity retains archive checksum verification and exact binary-version validation. Verifier tests update the fixture reference while retaining rejection cases for malformed and inconsistent responses. ✅ Permission compatibility supported — The supplied launch paths retain permission bypass for Claude tasks and goals, with empty native tools and restricted MCP configuration for repository inspection. The authoritative checks report 28 passed, none failed or pending, and 27 neutral/skipped. This was a static review; no commands were run. The linked objective is truncated, so requirements beyond its visible text could not be assessed. Merge blockersNo merge blockers. SuggestionsThese are optional follow-ups and are not sent to No suggestions. ScoreThe visible changes are coherent, appropriately scoped, and supported by passing current-head checks. No merge-blocking regression was demonstrated from the supplied diff and surrounding context. Score: 9/10 🤖 Review Details
🤖 Review by ProPR |
AI Implementation Summary
Closes #3574
Branch:
3574/claude-opus-5-5-bump-two-coding-agent-cli-20261115-0909-tpoCommits: ✅ Changes committed (8500636)
AI Processing Completed
Execution Details:
AGENT_DEFAULTS,version/types.ts, the root... #3574Summary:
I bumped Claude Code from 2.1.323 to 2.1.325 and Antigravity from 1.5.8 to 1.5.9, following the same touch list as #3527. Codex, Mistral Vibe and the model catalog are unchanged. Every suite I ran passed, including the runtime tool-policy test against the real 2.1.325 binary with nothing skipped.
Checks against the real releases
manifests/linux_amd64.jsonlists release4515810895593472with the SHA-512 from the issue. I downloaded the tarball: the checksum matches, it holds oneantigravityentry, and--versionprints1.5.9. The offlineagy changeloglists no model changes. It does confirm the newrun_workflowtool, which hands work to subagents from a Python script.latestdist-tag is 2.1.325 andstableis still 2.1.311. I compared the bundled model catalogs of the 2.1.323 and 2.1.325 binaries: they are identical. That means thenative_1mset inreviewContextBudget.tsonly needed its version comment updated.--dangerously-skip-permissions(dockerArgsBuilder.ts:176,claudeHelpers.ts:271).--setting-sources '', so the new rule about.claude/settings.local.jsonallow rules in containers doesn't matter./loop.What changed
Dockerfile.agent(both stages, plus Antigravity's release ID and SHA-512),scripts/build-images.sh,scripts/verify-antigravity-image.sh,AGENT_DEFAULTSinmodelDefinitions.ts, andversion/types.ts.package.jsonnow asks for^2.1.325. Thepackage-lock.jsondiff touches only the claude-code package and its 8 platform packages.THIRD_PARTY_LICENSES.md. The bundled license text is identical to 2.1.323's.modelDefinitions,versionService,nativeLogPolicy,reviewContextBudgetandreleaseImageFixtures. The verifier fixture is renamed fromantigravity-verifier-pinned-1.5.8.jsonto-1.5.9.json.managed-diagnostics.md,native-provider-log-policy.mdandpr-commands.md. I also added a short paragraph aboutrun_workflowtoagents-and-models.md.Test results
test/agentToolPolicyRuntime.test.ts(real 2.1.325, and Codex 0.168.0, both on PATH from/tmp)Changing the root lockfile doesn't require regenerating any checksums: this repo pins no lockfile checksums and has no qualification
SHA256SUMS, which live in propr-routing.For the PR description
run_workflowtool. On large headless tasks this may raise token use and run time.-p,--print-timeoutand exit codes are unchanged.claude-mythos-5-2, whichreviewContextBudget.tsdoesn't list. It was already in 2.1.323, isn't in ProPR's catalog, and the issue rules out catalog changes, so I left it alone.This change has no visible UI, so there are no previews.
Review digest
Risk-tiered paths
package-lock.json(+36/−36): lockfilepackage.json(+1/−1): dependency manifestDockerfile.agent(+6/−6)packages/core/src/agents/version/types.ts(+2/−2)packages/shared/src/modelDefinitions.ts(+2/−2)packages/shared/src/reviewContextBudget.ts(+1/−1)scripts/build-images.sh(+4/−4)scripts/verify-antigravity-image.sh(+1/−1)CHANGELOG.md(+15/−0)THIRD_PARTY_LICENSES.md(+4/−4)docs/docs/features/agents-and-models.md(+2/−0)docs/docs/features/pr-commands.md(+1/−1)docs/operations/managed-diagnostics.md(+2/−2)docs/operations/native-provider-log-policy.md(+2/−2)packages/core/test/nativeLogPolicy.test.ts(+1/−1)packages/core/test/versionService.test.ts(+2/−2)test/fixtures/antigravity-verifier-pinned-1.5.9.json(renamed, +1/−1)test/modelDefinitions.test.ts(+2/−2)test/releaseImageFixtures.test.ts(+8/−8)test/reviewContextBudget.test.ts(+1/−1)Validation evidence
Diff size: 20 files changed, +94/−77 lines
Detailed Logs:
16fa0df9-0055-461a-806e-4aaddc60ecb3Log files stored at:
/usr/src/app/logs/executions/issue-3574-2026-11-15T09-18-20-140Z-conversation.json/usr/src/app/logs/executions/issue-3574-2026-11-15T09-18-20-140Z-output.txtLatest Conversation Messages
This PR was created automatically by ProPR after processing issue #3574.
💡 Need changes?
Comment on this PR to request refinements — the AI agent monitors comments and will update the implementation based on your feedback. Keep iterating until you're satisfied!