chore: bump agentfield pin to >=0.1.84#75
Merged
Conversation
0.1.84 adds INFO-level diagnostics on the cross-reasoner pause- cascade path (agentfield#569). The flexible >=0.1.83 constraint on its own won't reinstall the SDK on the next Docker build because the cached `pip install` layer keys off file contents; changing the floor forces re-resolution. Bumped both requirements.txt AND requirements-docker.txt since the Dockerfile installs from the latter separately. Same playbook as the 0.1.82→0.1.83 round (PR #74 here). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Picks up agentfield 0.1.84 (release, merged PR).
What's in 0.1.84
INFO-level diagnostic logging on the cross-reasoner pause-propagation hot path. No behavior change; same imports, same control flow.
Why this PR is needed
Docker
pip installlayers are cached against file contents —>=0.1.83already permits 0.1.84, but unless the constraint string itself changes, the cached layer with 0.1.83 keeps getting restored on rebuild. Bumped bothrequirements.txtANDrequirements-docker.txtbecause the Dockerfile installs from the docker variant separately. Same playbook as the 0.1.82→0.1.83 round (PR #74).Test plan
railway ssh --service SWE-AF "pip show agentfield"returns 0.1.84