[PR #273] [MERGED] ci: use ubuntu-latest for non-release workflows #309

Closed
opened 2026-10-29 14:22:04 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/273
Author: @yingdi-shan
Created: 9/10/2026
Status: ✅ Merged
Merged: 9/11/2026
Merged by: @yingdi-shan

Base: main ← Head: ci/ubuntu-latest-non-release


📝 Commits (1)

  • 03b42ac ci: use ubuntu-latest for non-release workflows

📊 Changes

10 files changed (+17 additions, -22 deletions)

View changed files

📝 .github/workflows/benchmark.yml (+1 -2)
📝 .github/workflows/ci.yml (+3 -4)
📝 .github/workflows/coverage.yml (+2 -3)
📝 .github/workflows/e2b-benchmark.yml (+1 -1)
📝 .github/workflows/envd-tests.yml (+1 -1)
📝 .github/workflows/integration-tests.yml (+2 -4)
📝 .github/workflows/mutation-tests.yml (+1 -1)
📝 .github/workflows/publish-tools-image.yml (+4 -3)
📝 .github/workflows/services-ci.yml (+1 -1)
📝 .github/workflows/ublk-tests.yml (+1 -2)

📄 Description

What

Move 16 runner selections across 10 non-release workflows to ubuntu-latest.

Why

Keep CI on GitHub's current default Ubuntu image while preserving the older glibc build baseline for distributed release binaries. The Linux CLI and server release builds remain on Ubuntu 22.04.

None; small CI configuration update.

Scope and non-goals

Covers Rust CI, integration/E2E tests, envd tests, ublk tests, coverage, benchmarks, mutation tests, Go services CI, and the x64 tools-image publication jobs. The entire release workflow is unchanged.

The tools-image ARM build retains ubuntu-24.04-arm: GitHub's supported runner labels provide no ubuntu-latest ARM equivalent. A comment documents this exception.

Design and behavior changes

Only runner labels and their explanatory comments change. Remove comments explaining the superseded Ubuntu 22.04 ublk pins. Triggers, build/test commands, permissions, and architecture matrices retain their existing behavior.

Compatibility and operations

  • Public API or generated protocol: N/A; workflow-only change.
  • Configuration or defaults: Non-release x64 jobs now follow ubuntu-latest.
  • Snapshot manifest, artifact layout, or storage format: N/A.
  • Upgrade and rollback: No runtime migration; revert this PR to restore the prior CI runners.
  • Host requirements, permissions, ports, or dependencies: CI uses the packages and kernel shipped with ubuntu-latest. Release runner versions and the ARM tools-image runner remain pinned.

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:

git diff --check: PASS
actionlint 1.7.12, all 10 modified workflows, including ShellCheck: PASS
actionlint -shellcheck='', all 13 workflows: PASS
Inline Python/PyYAML comparison against origin/main: PASS
  - Exactly 16 runner selections changed.
  - release.yml is byte-identical.
  - ARM architecture is preserved.
  - No other parsed workflow values changed.
actionlint, all workflows: existing ShellCheck SC2317 in docs.yml:99
  - Reproduced against the unchanged main checkout.

Skipped checks and reasons: Rust/Go builds, runtime tests, code generation, and benchmarks were not run locally because only workflow runner settings changed. Actual runner compatibility requires GitHub-hosted CI execution.

Risks and reviewer notes

Draft pending hosted-runner validation. The previous pins documented an Ubuntu 24.04 / Linux 6.17 kernel crash in ublk ADD_DEV. This PR removes that workaround as part of switching to ubuntu-latest; it does not establish that the kernel issue is fixed. Verify the unit, ublk, and integration/E2E jobs before merging. Coverage and benchmark workflows also exercise ublk and need hosted-runner validation.

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.

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/AgentENV/pull/273 **Author:** [@yingdi-shan](https://github.com/yingdi-shan) **Created:** 9/10/2026 **Status:** ✅ Merged **Merged:** 9/11/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `ci/ubuntu-latest-non-release` --- ### 📝 Commits (1) - [`03b42ac`](https://github.com/kvcache-ai/AgentENV/commit/03b42acd62a1a729060978b885f9d574573e2d4f) ci: use ubuntu-latest for non-release workflows ### 📊 Changes **10 files changed** (+17 additions, -22 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/benchmark.yml` (+1 -2) 📝 `.github/workflows/ci.yml` (+3 -4) 📝 `.github/workflows/coverage.yml` (+2 -3) 📝 `.github/workflows/e2b-benchmark.yml` (+1 -1) 📝 `.github/workflows/envd-tests.yml` (+1 -1) 📝 `.github/workflows/integration-tests.yml` (+2 -4) 📝 `.github/workflows/mutation-tests.yml` (+1 -1) 📝 `.github/workflows/publish-tools-image.yml` (+4 -3) 📝 `.github/workflows/services-ci.yml` (+1 -1) 📝 `.github/workflows/ublk-tests.yml` (+1 -2) </details> ### 📄 Description ## What Move 16 runner selections across 10 non-release workflows to `ubuntu-latest`. ## Why Keep CI on GitHub's current default Ubuntu image while preserving the older glibc build baseline for distributed release binaries. The Linux CLI and server release builds remain on Ubuntu 22.04. ## Related issue None; small CI configuration update. ## Scope and non-goals Covers Rust CI, integration/E2E tests, envd tests, ublk tests, coverage, benchmarks, mutation tests, Go services CI, and the x64 tools-image publication jobs. The entire release workflow is unchanged. The tools-image ARM build retains `ubuntu-24.04-arm`: [GitHub's supported runner labels](https://docs.github.com/en/actions/reference/runners/github-hosted-runners) provide no `ubuntu-latest` ARM equivalent. A comment documents this exception. ## Design and behavior changes Only runner labels and their explanatory comments change. Remove comments explaining the superseded Ubuntu 22.04 ublk pins. Triggers, build/test commands, permissions, and architecture matrices retain their existing behavior. ## Compatibility and operations - Public API or generated protocol: N/A; workflow-only change. - Configuration or defaults: Non-release x64 jobs now follow `ubuntu-latest`. - Snapshot manifest, artifact layout, or storage format: N/A. - Upgrade and rollback: No runtime migration; revert this PR to restore the prior CI runners. - Host requirements, permissions, ports, or dependencies: CI uses the packages and kernel shipped with `ubuntu-latest`. Release runner versions and the ARM tools-image runner remain pinned. ## 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: ```text git diff --check: PASS actionlint 1.7.12, all 10 modified workflows, including ShellCheck: PASS actionlint -shellcheck='', all 13 workflows: PASS Inline Python/PyYAML comparison against origin/main: PASS - Exactly 16 runner selections changed. - release.yml is byte-identical. - ARM architecture is preserved. - No other parsed workflow values changed. actionlint, all workflows: existing ShellCheck SC2317 in docs.yml:99 - Reproduced against the unchanged main checkout. ``` Skipped checks and reasons: Rust/Go builds, runtime tests, code generation, and benchmarks were not run locally because only workflow runner settings changed. Actual runner compatibility requires GitHub-hosted CI execution. ## Risks and reviewer notes Draft pending hosted-runner validation. The previous pins documented an Ubuntu 24.04 / Linux 6.17 kernel crash in ublk `ADD_DEV`. This PR removes that workaround as part of switching to `ubuntu-latest`; it does not establish that the kernel issue is fixed. Verify the unit, ublk, and integration/E2E jobs before merging. Coverage and benchmark workflows also exercise ublk and need hosted-runner validation. ## 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 2026-10-29 14:22:04 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kvcache-ai/AgentENV#309
No description provided.