[PR #296] [MERGED] chore: bump tools version to 0.1.1

bsakaguchi commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/296
Author: @zlzGithub-0801
Created: 9/16/2026
Status: ✅ Merged
Merged: 9/16/2026
Merged by: @yingdi-shan

Base: main ← Head: chore/bump-tools-0.1.1

📝 Commits (1)

335f080 chore: bump tools version to 0.1.1

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 config/deps_manifest.toml (+1 -1)

📄 Description

What

Bump the default AgentENV tools version from 0.1.0 to 0.1.1.

Why

Use the latest tools release by default when building and deploying AgentENV.

N/A.

Scope and non-goals

This PR only updates the default tools version. It does not change runtime behavior, public APIs, configuration structure, or storage formats.

Design and behavior changes

AgentENV now resolves and packages tools version 0.1.1 instead of 0.1.0 by default.

Compatibility and operations

Public API or generated protocol: N/A.
Configuration or defaults: Default tools version changes from 0.1.0 to 0.1.1.
Snapshot manifest, artifact layout, or storage format: No changes.
Upgrade and rollback: Existing snapshots retain their recorded tools version. Rollback is possible by restoring the previous default version.
Host requirements, permissions, ports, or dependencies: No changes.

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

Validated Docker image build and deployment with tools version 0.1.1. Confirmed the prepared tools artifacts are present in the runtime image.

Skipped checks and reasons:

Full test suites were not run because this change only updates the default tools release version.

Risks and reviewer notes

The primary operational dependency is the availability and immutability of the 0.1.1 tools image in the configured registry. Existing snapshots continue using their recorded tools versions.

Checklist

The PR contains one coherent change and no unrelated formatting or refactoring.
New behavior is covered by validation, 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/296 **Author:** [@zlzGithub-0801](https://github.com/zlzGithub-0801) **Created:** 9/16/2026 **Status:** ✅ Merged **Merged:** 9/16/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `chore/bump-tools-0.1.1` --- ### 📝 Commits (1) - [`335f080`](https://github.com/kvcache-ai/AgentENV/commit/335f08068102b2af1ee1ef29110ab44ff92f0dbe) chore: bump tools version to 0.1.1 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `config/deps_manifest.toml` (+1 -1) </details> ### 📄 Description ## What Bump the default AgentENV tools version from `0.1.0` to `0.1.1`. ## Why Use the latest tools release by default when building and deploying AgentENV. ## Related issue N/A. ## Scope and non-goals This PR only updates the default tools version. It does not change runtime behavior, public APIs, configuration structure, or storage formats. ## Design and behavior changes AgentENV now resolves and packages tools version `0.1.1` instead of `0.1.0` by default. ## Compatibility and operations - Public API or generated protocol: N/A. - Configuration or defaults: Default tools version changes from `0.1.0` to `0.1.1`. - Snapshot manifest, artifact layout, or storage format: No changes. - Upgrade and rollback: Existing snapshots retain their recorded tools version. Rollback is possible by restoring the previous default version. - Host requirements, permissions, ports, or dependencies: No changes. ## Validation - [x] `make fmt` - [x] `make clippy` - [x] `make test-unit` - [x] 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 Validated Docker image build and deployment with tools version `0.1.1`. Confirmed the prepared tools artifacts are present in the runtime image. Skipped checks and reasons: Full test suites were not run because this change only updates the default tools release version. ## Risks and reviewer notes The primary operational dependency is the availability and immutability of the `0.1.1` tools image in the configured registry. Existing snapshots continue using their recorded tools versions. ## Checklist - [x] The PR contains one coherent change and no unrelated formatting or refactoring. - [x] New behavior is covered by validation, 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