Skip to content

chore: require prime-runs 0.1.5 from PyPI - #3001

Merged
kcoopermiller merged 2 commits into
mainfrom
chore/prime-runs-0.1.5-pypi
Oct 29, 2026
Merged

kcoopermiller merged 2 commits into
mainfrom
chore/prime-runs-0.1.5-pypi

Conversation

@kcoopermiller

@kcoopermiller kcoopermiller commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Summary

Replaces the git pins added in #2980 with the PyPI release of PrimeIntellect-ai/prime#1109 (orjson-encoded records and numpy streams). That release is PrimeIntellect-ai/prime#1126, which ships prime-runs 0.1.5 and prime-traces 0.0.11.

Both are now on PyPI. uv.lock moves prime-runs and prime-traces from the adf8d25c git sources to PyPI 0.1.5 / 0.0.11. No other package moves. The lockfile also changes from revision = 4 to 5, because uv 0.13 writes default-groups into it.

Changes

  • prime-runs>=0.1.4 → prime-runs>=0.1.5.
  • Removes the prime-runs git source in [tool.uv.sources], pinned to adf8d25c.
  • Removes the prime-traces git override in override-dependencies, pinned to the same commit. prime-runs 0.1.5 requires prime-traces>=0.0.11, so verifiers no longer needs to pin it.
  • Adds prime-traces = false to [tool.uv.exclude-newer-package]. Without it, the 7-day exclude-newer cooldown hides prime-traces 0.0.11 and the lock fails to resolve. prime-runs is already exempt.

Checks

  • In a fresh venv, pip install prime-runs==0.1.5 resolves prime-traces 0.0.11.
  • uv sync installs prime-runs 0.1.5 and prime-traces 0.0.11.
  • ruff check . passes.
  • tests/unit: 243 passed, 10 skipped. The skips need harbor or PRIME_API_KEY.

🤖 Generated with Claude Code

Note

Require prime-runs 0.1.5 from PyPI

Bumps the minimum prime-runs version to 0.1.5 in pyproject.toml and removes the uv sources and override-dependencies entries that pulled prime-runs and prime-traces from specific Git revisions. Adds prime-traces = false to tool.uv.exclude-newer-package so the cutoff does not apply to it. Behavioral Change: both packages now resolve from PyPI instead of pinned Git commits.

Changes since #3001 opened

  • Updated the dependency lock to require prime-runs version 0.1.5 from PyPI. [2d3f59a]

Macroscope summarized 1b749f4.


Note

Low Risk
Dependency and lockfile-only change with no application code edits; behavior shifts from pinned git commits to released PyPI versions already exercised via the prior pins.

Overview
This PR drops temporary git pins for prime-runs and prime-traces and consumes the published PyPI releases instead (prime-runs 0.1.5, prime-traces 0.0.11 via prime-runs' dependency).

pyproject.toml raises the minimum to prime-runs>=0.1.5, removes the prime-runs git entry under [tool.uv.sources], removes the prime-traces git override-dependencies block (and related TODO comments), and adds prime-traces = false to [tool.uv.exclude-newer-package] so the 7-day exclude-newer window does not block resolving the new trace package.

uv.lock reflects PyPI sources for both packages, drops the manifest override for prime-traces, and bumps lock revision to 5 (uv writing default-groups on the root package).

Reviewed by Cursor Bugbot for commit 2d3f59a. Bugbot is set up for automated code reviews on this repo. Configure here.

Replaces the git pins on PrimeIntellect-ai/prime@adf8d25c (prime-runs source
and prime-traces override) with the PyPI release that ships #1109. prime-traces
joins the exclude-newer exemptions so 0.0.11 resolves inside the 7-day window.

uv.lock still needs regenerating once prime-runs 0.1.5 and prime-traces 0.0.11
are on PyPI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kennethnym
kennethnym previously approved these changes Oct 29, 2026
@kcoopermiller
kcoopermiller marked this pull request as ready for review October 29, 2026 18:00
Both are now on PyPI (PrimeIntellect-ai/prime#1126). prime-runs and
prime-traces move from the adf8d25c git sources to the registry; no other
package moves.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@macroscopeapp

macroscopeapp Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Approved at 2d3f59a

Macroscope's review found this PR approvable — Replaces temporary Git pins with published prime-runs and prime-traces releases, without unrelated dependency upgrades or changes to upload controls. Reported installation and unit-test checks support this bounded packaging change.

Notes:

  • All code in this push has already been reviewed. Approvability was decided on eligibility alone.

You can add or adjust custom eligibility rules. Learn more.

@kcoopermiller
kcoopermiller merged commit 3ff4496 into main Oct 29, 2026
61 of 63 checks passed
@kcoopermiller
kcoopermiller deleted the chore/prime-runs-0.1.5-pypi branch October 29, 2026 18:15
mikasenghaas added a commit to PrimeIntellect-ai/prime-rl that referenced this pull request Nov 2, 2026
## Summary

- Bump `prime-sandboxes` 0.5.1 → 0.5.3 so live sandbox processes are no
longer capped at 24h (via PrimeIntellect-ai/verifiers#3043).
- Bump `deps/verifiers` `60290d4` → `bccc2c5` (verifiers main, with
PrimeIntellect-ai/verifiers#3043 merged).
- Require `prime-runs[train]>=0.1.5` from PyPI. This drops the
`prime-runs` git source and the `prime-traces` git override, both pinned
to `adf8d25c`. The new verifiers requires `prime-runs>=0.1.5`
(PrimeIntellect-ai/verifiers#3001), and the old git pin no longer
resolves. 0.1.5 contains `adf8d25c`, so it includes
PrimeIntellect-ai/prime#1109. `uv.lock`: `prime-runs` 0.1.4 (git) →
0.1.5, `prime-traces` 0.0.10 (git) → 0.0.11.

### Why

On Prime, the SDK sent a fixed 24h deadline on every live process
stream, and the sandbox ended the process when it expired. A long agent
segment then lost its ACP process. The trace stopped as `harness_error`
(`EOFError: ACP process closed its stdout`) instead of `agent_timeout`,
so `agent_timeout` undercounted real 24h cap hits.

### prime-sandboxes changes (0.5.1 → 0.5.3)

0.5.3:
- fix(sandboxes): stop capping live processes at 24h
(PrimeIntellect-ai/prime#1142)

0.5.2:
- feat(sandbox): add localhost forwards to the CLI and SDK
(PrimeIntellect-ai/prime#1124)
- feat(sandboxes): add pause and resume to the SDK and CLI
(PrimeIntellect-ai/prime#1056)
- fix(cli): write credential files owner-only
(PrimeIntellect-ai/prime#1130); the SDK auth cache is written 0600

### verifiers changes (`60290d4` → `bccc2c5`)

Fixes and features:
- fix(serve): discard kept episodes when clients disconnect
(PrimeIntellect-ai/verifiers#2997)
- Reuse interception tunnels for task-scoped MCP servers
(PrimeIntellect-ai/verifiers#3006)
- Run Prime task services as native VMs and fix Harbor setup
(PrimeIntellect-ai/verifiers#2910)
- Run Compose services as native Prime VMs
(PrimeIntellect-ai/verifiers#2918)
- Accept Harbor Compose tasks on native VMs
(PrimeIntellect-ai/verifiers#2999)
- Add a native Compose integration test on Prime
(PrimeIntellect-ai/verifiers#3010)
- fix(harbor): reject ignored verifier user overrides
(PrimeIntellect-ai/verifiers#3014)
- Honor configured disk size for native Compose sidecars
(PrimeIntellect-ai/verifiers#3018)
- Size native Compose disks per service
(PrimeIntellect-ai/verifiers#3020)
- fix: use apk-installed Node and npm on Alpine
(PrimeIntellect-ai/verifiers#3004)
- fix: retry Node downloads before extracting
(PrimeIntellect-ai/verifiers#3005)
- fix(CVE-2026-111497) in Brotli and Node
(PrimeIntellect-ai/verifiers#2998)

Dependency pins:
- bump prime-sandboxes to 0.5.3 (PrimeIntellect-ai/verifiers#3043)
- chore: require prime-runs 0.1.5 from PyPI
(PrimeIntellect-ai/verifiers#3001)

Harness versions:
- Bump Codex to 0.166.0 and codex-acp to 2.5.0
(PrimeIntellect-ai/verifiers#3021)
- Bump DeepSeek harness to 0.2.1-rc.5 (PrimeIntellect-ai/verifiers#3023)
- Bump mini-swe-agent's LiteLLM dependency to 1.106.6
(PrimeIntellect-ai/verifiers#3031)
- Bump Hermes Agent to v0.22.5 (PrimeIntellect-ai/verifiers#3024)
- Bump Claude Code to 2.1.314 and claude-agent-acp to 0.99.1
(PrimeIntellect-ai/verifiers#3022)
- Bump Kimi Code to 2.4.1 (PrimeIntellect-ai/verifiers#3025)
- Bump OpenCode to 2.2.5 (PrimeIntellect-ai/verifiers#3026)
- Bump OpenClaw to 2026.10.9 (PrimeIntellect-ai/verifiers#3027)
- Bump Prime Agent to 0.10.2 (PrimeIntellect-ai/verifiers#3028)
- Bump nano-rlm to e4d4407f (PrimeIntellect-ai/verifiers#3029)
- Bump Terminus 2 to Harbor 0.25.0 (PrimeIntellect-ai/verifiers#3030)

Dependabot lockfile bumps in verifiers (they do not change prime-rl's
lock):
- urllib3 2.7.0 → 2.8.0 (PrimeIntellect-ai/verifiers#2733), pyjwt 2.13.0
→ 2.15.0 (PrimeIntellect-ai/verifiers#2735), opentelemetry-api 1.44.0 →
1.45.1 (PrimeIntellect-ai/verifiers#2964), authlib 1.7.2 → 1.9.1
(PrimeIntellect-ai/verifiers#2990), msgpack 1.2.1 → 1.2.3
(PrimeIntellect-ai/verifiers#2991), litellm 1.98.0 → 1.100.4
(PrimeIntellect-ai/verifiers#2992), dnspython 2.8.0 → 2.9.0
(PrimeIntellect-ai/verifiers#2993), filelock 3.32.4 → 4.2.1
(PrimeIntellect-ai/verifiers#3002), virtualenv 21.14.12 → 21.14.13
(PrimeIntellect-ai/verifiers#3008), joserfc 1.7.4 → 1.7.6
(PrimeIntellect-ai/verifiers#3017), oauthlib 3.3.1 → 4.0.0
(PrimeIntellect-ai/verifiers#3035)

## Verification

- `uv sync --frozen --all-packages --all-extras` installs
`prime-sandboxes` 0.5.3.
`prime_sandboxes.sandbox._LIVE_PROCESS_NO_TIMEOUT_MS == 9999999999` is
the default deadline for every `open_process` stream.
- `uv.lock` changes only `prime-sandboxes`, `prime-runs` and
`prime-traces` (plus a uv-written reorder of the `exclude-newer-package`
table).
- `pytest tests/unit --ignore=tests/unit/train`: 837 passed, 1 xfailed.
- `tests/unit/train` (RTX PRO 6000 Blackwell, SM120):
`qwen3_8_flash_next` and `test_fp8_grouped_gemm` show the same failures,
and `test_fused_lm_head.py::test_inject_prime_lm_head_vanilla` kills the
process, on this branch and on `main` (`823ed27`). These GPU kernel
tests do not touch this diff.
- verifiers#3043: the live Prime runtime tests
(`tests/unit/test_runtimes.py -k prime`, including `test_exec` on a live
process) pass on 0.5.3.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants