[PR #275] [MERGED] chore(release): bump version to v0.2.1

bsakaguchi commented

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

Owner

📋 Pull Request Information

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

Base: main ← Head: chore/release-0.2.1

📝 Commits (1)

4cc0847 chore(release): bump version to v0.2.1

📊 Changes

2 files changed (+3 additions, -3 deletions)

View changed files

📝 Cargo.lock (+2 -2)
📝 Cargo.toml (+1 -1)

📄 Description

What

Bump the shared workspace version from 0.2.0 to 0.2.1 for agentenv and aenv, and update their Cargo.lock entries.

Why

Prepare the v0.2.1 release so package metadata, the CLI version, and the server's node identity agree with the release tag.

N/A — release version bump.

Scope and non-goals

Three version values across Cargo.toml and Cargo.lock. Release publication follows the existing tagged-release workflow.

Design and behavior changes

Both release packages inherit workspace.package.version. The CLI version and server node identity derive from that package version.

Compatibility and operations

Public API or generated protocol: Version reporting changes to 0.2.1; schemas are unchanged.
Configuration or defaults: N/A — metadata only.
Snapshot manifest, artifact layout, or storage format: N/A — metadata only.
Upgrade and rollback: Standard upgrade or rollback; no migrations.
Host requirements, permissions, ports, or dependencies: Unchanged; verified all other lockfile contents remain identical.

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                                      passed
make fmt                                             passed
make clippy                                          passed
cargo test --locked -p aenv --bin aenv                 55 passed
cargo run --locked -p aenv -- --version                aenv 0.2.1
cargo metadata --no-deps --locked --format-version 1   passed

Verified agentenv and aenv resolve to 0.2.1 in Cargo metadata and the lockfile, and that all other lockfile contents are unchanged. Build checks reused the local Cargo target directory; CLI tests used isolated temporary state and dependency paths.

Skipped checks and reasons: The full unit target and VM integration suites are unnecessary for this metadata-only change; focused CLI tests and workspace Clippy cover the affected build. Go tests, code generation, documentation updates, and benchmarks are not applicable.

Risks and reviewer notes

Low risk: the diff matches the previous release bump's two-file scope and contains no dependency upgrades.

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/275 **Author:** [@yingdi-shan](https://github.com/yingdi-shan) **Created:** 9/11/2026 **Status:** ✅ Merged **Merged:** 9/11/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `chore/release-0.2.1` --- ### 📝 Commits (1) - [`4cc0847`](https://github.com/kvcache-ai/AgentENV/commit/4cc084774312f1a3290ae95ea4e03107948a4234) chore(release): bump version to v0.2.1 ### 📊 Changes **2 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `Cargo.lock` (+2 -2) 📝 `Cargo.toml` (+1 -1) </details> ### 📄 Description ## What Bump the shared workspace version from `0.2.0` to `0.2.1` for `agentenv` and `aenv`, and update their `Cargo.lock` entries. ## Why Prepare the `v0.2.1` release so package metadata, the CLI version, and the server's node identity agree with the release tag. ## Related issue N/A — release version bump. ## Scope and non-goals Three version values across `Cargo.toml` and `Cargo.lock`. Release publication follows the existing tagged-release workflow. ## Design and behavior changes Both release packages inherit `workspace.package.version`. The CLI version and server node identity derive from that package version. ## Compatibility and operations - Public API or generated protocol: Version reporting changes to `0.2.1`; schemas are unchanged. - Configuration or defaults: N/A — metadata only. - Snapshot manifest, artifact layout, or storage format: N/A — metadata only. - Upgrade and rollback: Standard upgrade or rollback; no migrations. - Host requirements, permissions, ports, or dependencies: Unchanged; verified all other lockfile contents remain identical. ## Validation - [x] `make fmt` - [x] `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 passed make fmt passed make clippy passed cargo test --locked -p aenv --bin aenv 55 passed cargo run --locked -p aenv -- --version aenv 0.2.1 cargo metadata --no-deps --locked --format-version 1 passed ``` Verified `agentenv` and `aenv` resolve to `0.2.1` in Cargo metadata and the lockfile, and that all other lockfile contents are unchanged. Build checks reused the local Cargo target directory; CLI tests used isolated temporary state and dependency paths. Skipped checks and reasons: The full unit target and VM integration suites are unnecessary for this metadata-only change; focused CLI tests and workspace Clippy cover the affected build. Go tests, code generation, documentation updates, and benchmarks are not applicable. ## Risks and reviewer notes Low risk: the diff matches the previous release bump's two-file scope and contains no dependency upgrades. ## 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