fix(agent-image): native pinned uv relock + bump uv to 0.11.7 - #48
Merged
Conversation
The relock never worked: the astral uv container image is distroless (no shell/git/python), so it cannot resolve the hermes-agent git+https dependency. Run pinned uv on the runner instead (which has git + python), with UV_FROZEN=false so the lock is actually written. Bump uv 0.5.0 -> 0.11.7 in lockstep across the relock workflow and the Dockerfile UV_VERSION (no published lock exists yet, so it's a clean slate -- no reason to stay on the old version). Makefile target now uses native uv too. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
stubbi
enabled auto-merge (squash)
June 1, 2026 09:05
stubbi
pushed a commit
that referenced
this pull request
Jun 3, 2026
🤖 I have created a release *beep* *boop* --- ## [0.1.10](v0.1.9...v0.1.10) (2026-06-03) ### Bug Fixes * **agent-image:** native pinned uv relock + bump uv to 0.11.7 ([#48](#48)) ([6e2615f](6e2615f)) * **agent-image:** relock uses uv image entrypoint (unblocks hermes-agent publish) ([#46](#46)) ([9e456b1](9e456b1)) * **agent-image:** verify uv.lock by git tag (unblocks publish) ([#50](#50)) ([3cbcc7f](3cbcc7f)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: paperclip-release-bot[bot] <288053502+paperclip-release-bot[bot]@users.noreply.github.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
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.
Follow-up to #46. The relock still couldn't run: the
ghcr.io/astral-sh/uvimage is distroless (no shell, git, or python), so it can't resolve thehermes-agent @ git+https://...source dependency at all (Could not read ELF interpreter …).UV_FROZEN=false(pyproject setsfrozen=truefor builds; relock must be allowed to write the lock).0.5.0→0.11.7in lockstep across the relock workflow and the DockerfileUV_VERSION. The only constraint is relock-uv == build-uv (lockfile-format compatibility); since no lock/image has ever been published, there's no legacy to stay compatible with — no reason to stay on the old version.agent-image-relocktarget switched to native uv as well.After merge: dispatch
agent-image-relock v0.13.0→ should now produce a realuv.lock→ PR/merge it → publish → make package public.🤖 Generated with Claude Code