Repository navigation
deps: raise the agentfield floor to 0.1.145 and keep the AForge harness - #80
Merged
Merged
Conversation
agentfield 0.1.143+ runs CodeAF for unpinned `aforge` requests. Setting AFORGE_BIN keeps this image on the aforge binary it ships, on purpose, until this product's own CodeAF migration. Older SDKs already honour AFORGE_BIN, so this changes nothing on its own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docker layer caching keys on the requirement text, so `agentfield>=0.1.130` kept restoring a layer built with an old SDK. Raising the floor invalidates that layer and picks up the current stable release. Co-Authored-By: Claude Opus 5.5 <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
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.
Why
Docker layer caching keys on the exact requirement text, so the old
agentfield>=floor kept restoring an image layer built with an older SDK. This raises the floor to the current stable release, 0.1.145, so the next build re-resolves it.Stays on AForge on purpose
Since agentfield 0.1.143, the SDK runs CodeAF for
provider="aforge"unlessAFORGE_BINis set (build_providerinsdk/python/agentfield/harness/providers/_factory.py). This image ships aforge at/usr/local/bin/aforgebut never setAFORGE_BIN, so the bump alone would have switched it to CodeAF. The first commit setsENV AFORGE_BIN=/usr/local/bin/aforge; older SDKs already honour it, so that commit changes nothing on its own.This product stays on AForge on purpose. Moving it to CodeAF is a separate change.
Verification
AFORGE_BINis set,build_providerreturnsAforgeProvider, andAforgeProviderusesAFORGE_BINas the binary path (providers/aforge.py).docker buildjob builds this image.🤖 Generated with Claude Code