Repository navigation
chore(tasks): bump sandbox @posthog/agent to 2.4.257 - #114211
Conversation
scheduled-actions-posthog
Bot
added
dependencies
|
😎 Merged successfully - details. |
|
Risk: No findings This PR bumps the sandbox base image's pinned Sentinel reviewed |
👀 Auto-assigned reviewersThese soft owners were skipped because they only have minor changes here. Nothing blocks merge, so self-assign if you'd like a look:
Soft owners come from each directory's |
🤖 CI report
|
![releaser-posthog[bot]](https://avatars.githubusercontent.com/in/2498497?s=60&v=4){kind=small}
|
/trunk merge |
Problem
The sandbox base image pins
@posthog/agentso a published release reaches production sandboxes only through a commit onmaster. That pin is at2.4.256; the release published2.4.257.Changes
Dockerfile.sandbox-base:AGENT_VERSION2.4.256to2.4.257;AGENT_TARBALL_SHA256set to the digest of theagent-v2.4.257release tarball.The sandbox image workflow waits for
2.4.257to be published, builds this image and smokes it on both architectures. This workflow then runs one Claude turn and one Codex turn with that image through the production Go ai-gateway. When both checks pass, the release app approves this PR and adds it to the merge queue. Close it before the queue lands it to keep2.4.256. A newer release opens its own PR and closes this one.What this ships
Agent commits between
agent-v2.4.256andagent-v2.4.257(compare): 8Dependency changes
None.
How did you test this code?
The sandbox image CD workflow builds this PR's image on both architectures, checks that the installed
@posthog/agentmatches the pin, and runs theagent-serverentrypoint. That covers packaging and dependency resolution. This workflow then drives one Claude turn and one Codex turn from the image through the US Go ai-gateway, on the default models and efforts, and needs both to read a file with a tool. The agent's own test suite ran before the release was published.