From 94ed1e0f96892cc63ecfa8c226910e8fdafe8d84 Mon Sep 17 00:00:00 2001 From: Imran Siddique Date: Mon, 27 Jul 2026 21:14:43 -0700 Subject: [PATCH] chore(release): 0.4.0 Publishes the TRACE v0.2 conformance cutover. Major-ish for a 0.x: the suite now fails a record carrying the v0.1 profile URI, so anything emitting v0.1 records must stay on 0.3.x. Producers cannot move to v0.2 until this is on PyPI, since they run this suite against their own output. Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 2 ++ pyproject.toml | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 5e3e3b6..3b17422 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,8 @@ ## Unreleased +## v0.4.0 — 2026-07-28 + ### Changed - **BREAKING: the suite now conforms to TRACE v0.2.** `TR-ENV` requires the profile `tag:agentrust-io.com,2026:trace-v0.2` and fails a record carrying the v0.1 identifier. The v0.1 URI named `agentrust.io`, a domain this project never controlled, which RFC 4151 does not permit for a tag URI; see agentrust-io/trace-spec#107. Nothing else about the record format changed, so a producer migrates by updating the profile string and bumping `agentrust-trace` to 0.5.0. diff --git a/pyproject.toml b/pyproject.toml index 6fe8009..9955574 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "hatchling.build" [project] name = "agentrust-trace-tests" -version = "0.3.0" +version = "0.4.0" description = "TRACE conformance test suite" readme = "README.md" license = { text = "Apache-2.0" }