[PR #149] [MERGED] chore(release): bump version to v0.1.2 #211

New issue

Closed

opened 2026-10-29 14:21:03 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

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

Owner

📋 Pull Request Information

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

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

📝 Commits (1)

0ba95de chore(release): bump version to v0.1.2

📊 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.1 to 0.1.2.
Refresh the agentenv and aenv entries in Cargo.lock.

Why

Prepare the workspace for the v0.1.2 release. The release workflow validates both package versions against the pushed tag before building and publishing artifacts.

Scope and non-goals

This PR changes release metadata only. It does not change runtime behavior, APIs, configuration, or dependencies.

Design and behavior changes

N/A; version metadata only.

Compatibility and operations

Public API or generated protocol: N/A
Configuration or defaults: N/A
Snapshot manifest, artifact layout, or storage format: N/A
Upgrade and rollback: N/A
Host requirements, permissions, ports, or dependencies: N/A

After merge, pushing v0.1.2 will trigger the release workflow that builds artifacts, publishes images, generates release notes, and creates the GitHub release.

Risks and reviewer notes

Low risk. Confirm this PR is merged before creating the v0.1.2 tag; tagging an earlier commit would fail release version 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/149 **Author:** [@yingdi-shan](https://github.com/yingdi-shan) **Created:** 8/10/2026 **Status:** ✅ Merged **Merged:** 8/10/2026 **Merged by:** [@yingdi-shan](https://github.com/yingdi-shan) **Base:** `main` ← **Head:** `chore/release-v0.1.2` --- ### 📝 Commits (1) - [`0ba95de`](https://github.com/kvcache-ai/AgentENV/commit/0ba95dece4c13bebf0a176b23fe1801182281204) chore(release): bump version to v0.1.2 ### 📊 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.1 to 0.1.2. - Refresh the agentenv and aenv entries in Cargo.lock. ## Why Prepare the workspace for the v0.1.2 release. The release workflow validates both package versions against the pushed tag before building and publishing artifacts. ## Scope and non-goals This PR changes release metadata only. It does not change runtime behavior, APIs, configuration, or dependencies. ## Design and behavior changes N/A; version metadata only. ## Compatibility and operations - Public API or generated protocol: N/A - Configuration or defaults: N/A - Snapshot manifest, artifact layout, or storage format: N/A - Upgrade and rollback: N/A - Host requirements, permissions, ports, or dependencies: N/A After merge, pushing v0.1.2 will trigger the release workflow that builds artifacts, publishes images, generates release notes, and creates the GitHub release. ## Risks and reviewer notes Low risk. Confirm this PR is merged before creating the v0.1.2 tag; tagging an earlier commit would fail release version 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:21:03 +00:00