Skip to content

Prepare v0.3.0 release #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
askmy-stack merged 1 commit into from
Aug 13, 2026
Merged

Prepare v0.3.0 release #52

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,19 @@ All notable changes to Tool-Semantics will be documented in this file.
### Added
- (none yet)

## [0.3.0] — 2026-08-12

### Added
- Optional redacted provenance sidecars for `capture` and `capture-mcp`
snapshots via `--provenance-output`
- Git-tracked approved-baseline workflow documentation for compatibility checks
- Optional `upload-artifacts` support in the composite GitHub Action, preserving
the candidate snapshot and Markdown/JSON comparison reports

### Security
- Redact secret-like command arguments and command-form environment assignments
from provenance sidecars

## [0.2.0] — 2026-08-10

First PyPI release. Install with `pip install tool-semantics`.
Expand Down
6 changes: 3 additions & 3 deletions docs/github-action.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ askmy-stack/tool-semantics/.github/actions/compare
## Versioning the Action

Pin the composite Action to a **release tag** (or commit SHA) so consumer CI stays
reproducible. Tags follow the package version (`v0.2.0`, …). A floating major pin
reproducible. Tags follow the package version (`v0.3.0`, …). A floating major pin
such as `@v0` is fine once a `v0` moving tag exists; prefer an exact tag for
production workflows.

Expand Down Expand Up @@ -43,9 +43,9 @@ jobs:
# committed before this pull request.
- name: Capture candidate snapshot
run: |
pip install "tool-semantics==0.2.0"
pip install "tool-semantics==0.3.0"
tool-semantics capture manifests/candidate.json -o .tool-semantics/candidate.json
- uses: askmy-stack/tool-semantics/.github/actions/compare@v0.2.0
- uses: askmy-stack/tool-semantics/.github/actions/compare@v0.3.0
with:
baseline: .tool-semantics/baselines/github.json
candidate: .tool-semantics/candidate.json
Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "hatchling.build"

[project]
name = "tool-semantics"
version = "0.2.0"
version = "0.3.0"
description = "Behavioral compatibility testing for MCP tools and AI-agent interfaces"
readme = "README.md"
requires-python = ">=3.11"
Expand Down
2 changes: 1 addition & 1 deletion src/tool_semantics/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
"""Tool-Semantics: behavioral compatibility testing for MCP tools and AI-agent interfaces."""

__version__ = "0.2.0"
__version__ = "0.3.0"