[PR #243] [MERGED] chore(release): bump version to v0.2.0

bsakaguchi commented

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

Owner

📋 Pull Request Information

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

Base: main ← Head: chore/release-v0.2.0

📝 Commits (1)

2903cfb chore(release): bump version to v0.2.0

📊 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 package version from 0.1.3 to 0.2.0.
Update the aenv and agentenv package entries in Cargo.lock.

Why

Prepare the workspace for the v0.2.0 release.

N/A. This is release maintenance.

Scope and non-goals

This PR changes release metadata only. It does not alter runtime behavior, APIs, dependencies, documentation, or generated code.

Design and behavior changes

N/A. Package behavior is unchanged.

Compatibility and operations

Public API or generated protocol: N/A; no API or protocol changes.
Configuration or defaults: N/A; no configuration changes.
Snapshot manifest, artifact layout, or storage format: N/A; no format changes.
Upgrade and rollback: N/A; metadata-only release preparation.
Host requirements, permissions, ports, or dependencies: N/A; no operational changes.

After merge, pushing the v0.2.0 tag will trigger the release workflow.

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:

make fmt
# passed

cargo metadata --locked --format-version 1 --no-deps
# passed; agentenv and aenv resolve as 0.2.0

cargo check -p agentenv -p aenv --all-targets --locked
# passed

Skipped checks and reasons:

The broader lint, test, integration, generation, documentation, and benchmark checks were not run because this PR changes package version metadata only.

Risks and reviewer notes

Low risk. Confirm this PR is merged before creating the v0.2.0 tag.

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/243 **Author:** [@yingdi-shan](https://github.com/yingdi-shan) **Created:** 9/3/2026 **Status:** ✅ Merged **Merged:** 9/3/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `chore/release-v0.2.0` --- ### 📝 Commits (1) - [`2903cfb`](https://github.com/kvcache-ai/AgentENV/commit/2903cfb9938773c6e97e3b516c0919d3ba366bf5) chore(release): bump version to v0.2.0 ### 📊 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 package version from `0.1.3` to `0.2.0`. - Update the `aenv` and `agentenv` package entries in `Cargo.lock`. ## Why Prepare the workspace for the `v0.2.0` release. ## Related issue N/A. This is release maintenance. ## Scope and non-goals This PR changes release metadata only. It does not alter runtime behavior, APIs, dependencies, documentation, or generated code. ## Design and behavior changes N/A. Package behavior is unchanged. ## Compatibility and operations - Public API or generated protocol: N/A; no API or protocol changes. - Configuration or defaults: N/A; no configuration changes. - Snapshot manifest, artifact layout, or storage format: N/A; no format changes. - Upgrade and rollback: N/A; metadata-only release preparation. - Host requirements, permissions, ports, or dependencies: N/A; no operational changes. After merge, pushing the `v0.2.0` tag will trigger the release workflow. ## Validation - [x] `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 make fmt # passed cargo metadata --locked --format-version 1 --no-deps # passed; agentenv and aenv resolve as 0.2.0 cargo check -p agentenv -p aenv --all-targets --locked # passed ``` Skipped checks and reasons: The broader lint, test, integration, generation, documentation, and benchmark checks were not run because this PR changes package version metadata only. ## Risks and reviewer notes Low risk. Confirm this PR is merged before creating the `v0.2.0` tag. ## 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:21:49 +00:00