Skip to content

chore(deps): bump agentfield floor to 0.1.79#69

Merged
AbirAbbas merged 1 commit into
mainfrom
chore/bump-agentfield-0.1.79
May 8, 2026
Merged

chore(deps): bump agentfield floor to 0.1.79#69
AbirAbbas merged 1 commit into
mainfrom
chore/bump-agentfield-0.1.79

Conversation

@AbirAbbas
Copy link
Copy Markdown
Collaborator

Summary

Bumps the agentfield SDK floor from >=0.1.77 to >=0.1.79 across requirements.txt, requirements-docker.txt, and pyproject.toml.

Why this matters

0.1.79 contains the pause-aware reasoner-timeout fix (Agent-Field/agentfield#552). The build reasoner sits inside app.pause() while waiting for hax-sdk plan approvals, so any review that took longer than default_execution_timeout (7200s) was billed against the reasoner budget and surfaced as Reasoner 'build' timed out after 7200.0s. With 0.1.79, time spent in pause() is subtracted from elapsed before the watchdog compares against the budget.

Why bumping the constraint string is required

Docker layer caching keys off the requirements file contents. Leaving the constraint at >=0.1.77 would let the cached pip install layer keep installing whatever it last resolved (0.1.77) even though 0.1.79 is now on PyPI. Forcing the string to >=0.1.79 invalidates that layer and pulls the fix on the next image build.

Test plan

  • CI green
  • After merge, redeploy on Railway and confirm the new image was rebuilt (not pulled from cache)
  • Confirm agentfield resolves to 0.1.79+ in the running container (pip show agentfield)
  • Verify a long-running plan approval no longer trips the 7200s timeout

🤖 Generated with Claude Code

0.1.79 contains the pause-aware reasoner timeout fix
(Agent-Field/agentfield#552). The build reasoner sits inside
app.pause() while waiting for hax-sdk plan approvals, so any review
that took longer than default_execution_timeout (7200s) was billed
against the reasoner budget and surfaced as
"Reasoner 'build' timed out after 7200.0s".

The constraint string is what bumps it — Docker layer-cache keys off
the requirements file contents, so leaving it at >=0.1.77 would let
the cached pip-install layer keep installing 0.1.77 even though
0.1.79 is on PyPI. Forcing the string to >=0.1.79 invalidates that
layer and pulls the fix on the next build.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@AbirAbbas AbirAbbas merged commit 737fb50 into main May 8, 2026
2 checks passed
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