Repository navigation
chore(tasks): bump sandbox @posthog/agent to 2.4.305 - #126793
Merged
Merged
Conversation
scheduled-actions-posthog
Bot
added
dependencies
|
😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details. |
|
Risk: No findings This PR bumps the sandbox base image's Sentinel reviewed |
Contributor
🤖 CI report
|
![releaser-posthog[bot]](https://avatars.githubusercontent.com/in/2498497?s=60&v=4){kind=small}
|
/trunk merge |
HostHog preview —
|
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.
Problem
The sandbox base image pins
@posthog/agentso a published release reaches production sandboxes only through a commit onmaster. That pin is at2.4.304; the release published2.4.305.Changes
Dockerfile.sandbox-base:AGENT_VERSION2.4.304to2.4.305;AGENT_TARBALL_SHA256set to the digest of theagent-v2.4.305release tarball.The sandbox image workflow waits for
2.4.305to 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.304. A newer release opens its own PR and closes this one.What this ships
Agent commits between
agent-v2.4.304andagent-v2.4.305(compare): 1Dependency 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.