[PR #118] [MERGED] ci: publish multi-platform tools image

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/AgentENV/pull/118 **Author:** [@zlzGithub-0801](https://github.com/zlzGithub-0801) **Created:** 8/4/2026 **Status:** ✅ Merged **Merged:** 8/5/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `feat/tools-image-publish` --- ### 📝 Commits (1) - [`e9bd800`](https://github.com/kvcache-ai/AgentENV/commit/e9bd800c11e77beab3e50753798d3009fc523851) ci: publish multi-platform tools image ### 📊 Changes **6 files changed** (+141 additions, -14 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/publish-tools-image.yml` (+122 -0) 📝 `tests/integration/snapshot.rs` (+4 -1) 📝 `tests/integration/snapshot_attached_drive.rs` (+4 -1) 📝 `tools-image/Dockerfile` (+3 -4) 📝 `tools-image/Makefile` (+2 -2) 📝 `tools-image/README.md` (+6 -6) </details> ### 📄 Description ## What Add a publication workflow for the AgentENV tools image. ## Why Previously, tools image publication was a manual, local process. This workflow builds each platform on a native GitHub-hosted runner and publishes a multi-platform image to: `ghcr.io/<repository-owner>/agentenv-tools:<version>` ## Related issue  Closes # ## Scope and non-goals ### Included: - A new workflow for building and publishing multi-architecture tools images. ### not included: - Changes to the AgentENV runtime workflow. ## Design and behavior changes The `Publish Tools Image` workflow is triggered manually with two inputs: - `tools_version`: immutable SemVer version for the complete tools drive. - `envd_ref`: tag, branch, or commit from `e2b-dev/infra`. The workflow performs three stages: 1. Validate publication - Validates `tools_version` using the existing Makefile SemVer check. - Checks that the final GHCR tag does not already exist. 2. Build and push architecture images 3. Publish the multi-platform manifest ## Compatibility and operations  - Public API or generated protocol: N/A — no API or generated protocol changes. - Configuration or defaults: The tools producer default remains `0.1.0`; the default envd ref changes to `2026.17`, and the default Go builder changes to `1.25.9`. - Snapshot manifest, artifact layout, or storage format: N/A — no structural changes. - Upgrade and rollback: Published version tags are treated as immutable. Rollback is performed by configuring AgentENV to use an earlier tools version. - Host requirements, permissions, ports, or dependencies: Publication requires GitHub Actions package write access to the repository owner's `agentenv-tools` GHCR package. ## Validation  - [x] `make fmt` - [x] `make clippy` - [x] `make test-unit` - [x] Relevant Rust integration tests - [ ] `make -C services test` (required when `services/` changes) - [x] Generated clients/server regenerated with the documented `make` target - [x] Documentation updated - [ ] Benchmarks or performance comparison completed Commands and results: ```text ``` Skipped checks and reasons: - make -C services test: skipped because services/ was not changed. - Benchmarks: skipped because this change does not affect a runtime hot path or performance-sensitive behavior. ## Risks and reviewer notes  ## Checklist - [x] The PR contains one coherent change and no unrelated formatting or refactoring. - [x] New behavior is covered by tests, or I explained why testing is impractical. - [x] Logs and examples contain no credentials, tokens, or private registry information. - [x] I did not manually edit generated code without updating its source and regenerating it. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi commented

2026-10-29 14:20:49 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/118
Author: @zlzGithub-0801
Created: 8/4/2026
Status: ✅ Merged
Merged: 8/5/2026
Merged by: @yingdi-shan

Base: main ← Head: feat/tools-image-publish

📝 Commits (1)

e9bd800 ci: publish multi-platform tools image

📊 Changes

6 files changed (+141 additions, -14 deletions)

View changed files

➕ .github/workflows/publish-tools-image.yml (+122 -0)
📝 tests/integration/snapshot.rs (+4 -1)
📝 tests/integration/snapshot_attached_drive.rs (+4 -1)
📝 tools-image/Dockerfile (+3 -4)
📝 tools-image/Makefile (+2 -2)
📝 tools-image/README.md (+6 -6)

📄 Description

What

Add a publication workflow for the AgentENV tools image.

Why

Previously, tools image publication was a manual, local process.
This workflow builds each platform on a native GitHub-hosted runner and publishes a multi-platform image to:
ghcr.io/<repository-owner>/agentenv-tools:<version>

Closes #

Scope and non-goals

Included:

A new workflow for building and publishing multi-architecture tools images.

not included:

Changes to the AgentENV runtime workflow.

Design and behavior changes

The Publish Tools Image workflow is triggered manually with two inputs:

tools_version: immutable SemVer version for the complete tools drive.
envd_ref: tag, branch, or commit from e2b-dev/infra.

The workflow performs three stages:

Validate publication
- Validates tools_version using the existing Makefile SemVer check.
- Checks that the final GHCR tag does not already exist.
Build and push architecture images
Publish the multi-platform manifest

Compatibility and operations

Public API or generated protocol: N/A — no API or generated protocol changes.
Configuration or defaults: The tools producer default remains 0.1.0; the default envd ref changes to 2026.17, and the default Go builder changes to 1.25.9.
Snapshot manifest, artifact layout, or storage format: N/A — no structural changes.
Upgrade and rollback: Published version tags are treated as immutable. Rollback is performed by configuring AgentENV to use an earlier tools version.
Host requirements, permissions, ports, or dependencies: Publication requires GitHub Actions package write access to the repository owner's agentenv-tools GHCR package.

Validation

make fmt
make clippy
make test-unit
Relevant Rust integration tests
make -C services test (required when services/ changes)
Generated clients/server regenerated with the documented make target
Documentation updated
Benchmarks or performance comparison completed

Commands and results:

Skipped checks and reasons:

make -C services test: skipped because services/ was not changed.
Benchmarks: skipped because this change does not affect a runtime hot path or performance-sensitive behavior.

Risks and reviewer notes

Checklist

The PR contains one coherent change and no unrelated formatting or refactoring.
New behavior is covered by tests, or I explained why testing is impractical.
Logs and examples contain no credentials, tokens, or private registry information.
I did not manually edit generated code without updating its source and regenerating it.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

bsakaguchi

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-10-29 14:22:39 +00:00

[PR #341] feat(scheduler): add HA via Kubernetes Lease leader election #364

Rows
Columns

[PR #118] [MERGED] ci: publish multi-platform tools image #191