From 65d83160a5d7f0667c284f172e16c07c15fb71f6 Mon Sep 17 00:00:00 2001 From: Tom Ballard Date: Mon, 29 Jun 2026 19:52:13 +0000 Subject: [PATCH] chore(release): set version to 2026.06.1 [release:2026.06.1] MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Second release. Bumps package.json to the zero-padded CalVer 2026.06.1 (the workflow de-pads to 2026.6.1 for npm) and adds the 2026.06.1 CHANGELOG entry — the graph schema_version compatibility check, plus the move to OIDC publishing. Cut a GitHub Release tagged 2026.06.1 to publish (requires the npm trusted publisher configured for release.yml). Signed-off-by: Tom Ballard --- CHANGELOG.md | 6 ++++++ package.json | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 638556d..e3d84b7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -12,6 +12,12 @@ padding to a valid npm version (`2026.6.4`) at publish, because npm's strict SemVer forbids leading zeros. The release tag and `package.json` version must match exactly, or the workflow fails the publish. +## 2026.06.1 — the "contract guard" release + +Hardens the one dependency that matters: the Lore contract. Proofkeeper consumes rac-core only through the published `rac export --graph` contract, and now **checks the graph's `schema_version`** against the version it supports. A graph that declares an unsupported version is **refused with a clear, actionable error** instead of parsed best-effort; a graph that omits the field is tolerated. The supported version is documented and exported as `SUPPORTED_GRAPH_SCHEMA`. Per ADR-007 the engine bumps `schema_version` only on a breaking change, so this turns "should be compatible" into an explicit, checked guarantee — no silent, wrong coverage. + +Behind the scenes, releases now publish to npm via **Trusted Publishing (OIDC)** — no long-lived token. + ## 2026.06.0 — the "first proof" release The first cut of **Proofkeeper** — the open-source autonomous-QA agent for [Lore](https://github.com/itsthelore/rac-core), and the OSS answer to Factory's DROID, **bounded to verification**. Hand it real developer tools — a **browser, a terminal, and HTTP** — and **your own model**, and it drives your product to prove each capability works, then leaves **durable, re-runnable evidence** in a pull request. It does in the open what DROID's autonomous-QA half does behind closed doors. Lore records *what* your product should do (requirements as code); Proofkeeper proves it does, and proposes the evidence back for human review (ADR-083). diff --git a/package.json b/package.json index 08c9180..7123fa9 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@itsthelore/proofkeeper", - "version": "2026.06.0", + "version": "2026.06.1", "description": "Lore Proofkeeper — an autonomous QA agent that drives a product, compiles the session into durable Playwright tests, gates them on fidelity, and reports which Lore capabilities are unverified.", "license": "Apache-2.0", "type": "module",