chore(deps): bump the strands family (slice 2 of 3 from #19) - #22
Merged
Conversation
strands-agents 1.30/1.32 → 1.52.0, bedrock-agentcore 1.4 → 1.21.0, plus strands-agents-builder, ag-ui-strands 0.1.1 → 0.3.0 and PyJWT across the four strands-based patterns: strands-agent, research-agent, code-agent, agui-strands-agent. mcp stays 1.29.0 — #19 wanted 2.0.0, but strands-agents 1.52.0 itself requires mcp<2.0.0 (pip: ResolutionImpossible). agui-strands-agent's stale mcp==1.26.0 is aligned up to 1.29.0 while here. Verified (the checks GitHub CI cannot run): - arm64 container build + 'import agent' inside the image for all four patterns: strands 1.52.0, bedrock-agentcore 1.21.0 (code-agent resolves 1.22.0 from its >= range). - LIVE on the rig: deployed AGENT_PATTERN=strands-agent, UPDATE_COMPLETE, and an invoke returned all three tools (text_analysis_tool, WebSearch, execute_python_securely) plus a real gateway web-search answer with a cited URL — so the upgrade keeps the MCP client, the token-vault M2M path and the code interpreter working. - Rig restored to AGENT_PATTERN=orchestrator afterwards. Note: code-agent's Dockerfile builds from its OWN directory as context (COPY agent.py .), unlike the patterns that copy shared/ — a per-pattern build loop over agent-code/ fails on it. Left as-is; it matches its RuntimeStack source_dir.
|
Commit: Security Scan Results
|
This was referenced Aug 18, 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.
What
Slice 2 of 3 from #19: the four strands-based patterns —
strands-agent,research-agent,code-agent,agui-strands-agent.mcp stays at 1.29.0. #19 wanted 2.0.0, but
strands-agents 1.52.0itself requiresmcp<2.0.0, so that batch is uninstallable (pip … → ResolutionImpossible).Verified — the checks GitHub CI cannot run
import agentinside the image, all four patterns: strands 1.52.0, bedrock-agentcore 1.21.0.AGENT_PATTERN=strands-agent→ UPDATE_COMPLETE → invoke returned all three tools (text_analysis_tool,WebSearch,execute_python_securely) and a real gateway web-search answer with a cited URL. That exercises the MCP client, the AgentCore Identity M2M token-vault path, and the code interpreter on the new versions.AGENT_PATTERN=orchestratorafter the test.Note for maintainers
code-agent's Dockerfile builds from its own directory as context (COPY agent.py .), unlike patterns that copyshared/. A build loop overagent-code/fails on it — that's expected and matches itsRuntimeStack(source_dir=…).Next
Slice 3: the langchain/langgraph + claude-sdk patterns (
langgraph-agent,agui-langgraph-agent,claude-sdk-agent,claude-sdk-multi-agent) — the copilotkit/langchain constraint web, verified the same way.