Repository navigation
chore: require prime-runs 0.1.4 - #3928
Merged
Merged
Conversation
prime-runs 0.1.4 adds an opt-out of Prime Traces (PRIME_TRACES_OPT_OUT, the traces_opt_out config key, or init(traces_opt_out=True)). 0.1.3 ignores all three without a warning, so raise the floor and the lock to a version that honors them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kcoopermiller
marked this pull request as ready for review
October 8, 2026 01:11
hallerite
approved these changes
Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raises the
prime-runs[train]floor from>=0.1.3to>=0.1.4and updatesuv.lockto match.Why
prime-runs0.1.4 lets a run opt out of Prime Traces and upload its samples to the legacy sample tables instead (PrimeIntellect-ai/prime#998):PRIME_TRACES_OPT_OUT=trueprime config set-traces-opt-out true, which setstraces_opt_outin~/.prime/config.jsonprime_runs.init(traces_opt_out=True)prime-runs0.1.3 doesn't know about any of these. With 0.1.3 installed, which is whatuv syncgives today, a user who sets the environment variable or the config key gets no error and no warning, and their runs keep uploading to Prime Traces. Requiring 0.1.4 makes the setting take effect.Nothing changes for runs that don't opt out. The Prime monitor calls
prime_runs.init()without the new argument, so the default (upload to Prime Traces) is unchanged.A training run that opts out needs pyarrow for the legacy sample encoder. prime-rl already depends on
prime-runs[train], which includes it.Changes
pyproject.toml:prime-runs[train]>=0.1.3→prime-runs[train]>=0.1.4.uv.lock:prime-runs0.1.3 → 0.1.4. No other package moves;prime-tracesstays at 0.0.7.The
deps/verifierssubmodule is not changed. Its own floor is raised separately in PrimeIntellect-ai/verifiers#2805, and this PR doesn't depend on it.uv lock --checkpasses. I did not run the test suite.🤖 Generated with Claude Code
Note
Low Risk
Dependency floor bump only; no application code changes and default trace upload behavior stays the same.
Overview
Raises the
prime-runs[train]minimum from>=0.1.3to>=0.1.4inpyproject.tomland pinsprime-runs0.1.4 inuv.lock.This ensures installs pick up Prime Traces opt-out behavior (
PRIME_TRACES_OPT_OUT,prime config set-traces-opt-out, orprime_runs.init(traces_opt_out=True)), which 0.1.3 silently ignored so opted-out runs could still upload to Prime Traces. Default runs that do not opt out are unchanged;prime-rlstill depends on the[train]extra for legacy sample encoding when opting out.Reviewed by Cursor Bugbot for commit 06caa96. Bugbot is set up for automated code reviews on this repo. Configure here.