feat(agent-runner): track agent-kit releases and bump baked pin to v3.3.0#20
Merged
Merged
Conversation
Bump the baked agent-kit runtime pin from v1.1.0 to v3.3.0 across the agent-runner Dockerfile and the ci/publish build-args, and add a Renovate regex customManager that tracks these pins against agent-kit GitHub releases so a kit release opens a single grouped bump PR.
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
1 participant
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.
Addresses JorisJonkers-dev/agent-kit#25.
The agent-runner image baked the agent-kit runtime at v1.1.0 while the kit is at v3.3.0, and nothing bumped the pin on a kit release. This closes the propagation gap:
With this, a kit release yields a single grouped bump PR here; merging it releases a runner image on the new kit, which the agents-api idle-recycle mechanism then delivers to disconnected runners. Boot-time freshness (agent-kit#26) removes the recycle latency separately.
Reviewed cross-provider (codex) before opening: APPROVE, no findings. The v3.3.0 release tarball assets are confirmed present; the GHCR runtime-home OCI tag could not be verified from the sandbox (token lacks package read) but the Dockerfile falls back to the release tarball.