From 22613f763323d906ff6bd182f4a4281b8d6c7fe0 Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Fri, 7 Aug 2026 18:44:34 +0200 Subject: [PATCH] =?UTF-8?q?rivet:=20REQ-22=20shipped=20=E2=80=94=20crates.?= =?UTF-8?q?io=20publish=20live=20(verified,=20v0.10.0)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit crates.io backfilled to 0.10.0 (wsc, wsc-verify-core, wsc-attestation, wsc-cli) via the armed OIDC Trusted Publishing pipeline (#226 + workflow run 31197994842). Registry current for the first time since 0.9.0. Closes #220. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_012aR3Md1h46K9wAUWMQiESH --- artifacts/dev/features.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/artifacts/dev/features.yaml b/artifacts/dev/features.yaml index e3b6438..758911e 100644 --- a/artifacts/dev/features.yaml +++ b/artifacts/dev/features.yaml @@ -639,7 +639,7 @@ artifacts: - id: REQ-22 type: requirement title: crates.io publish rides the v* tag so the registry never lags a release - status: draft + status: verified description: "Per release-artifact-pipeline Track B: the release workflow publishes wsc (and member crates) to crates.io on the v* tag. Currently the registry serves 0.9.0 while v0.9.4 is released — four versions of library fixes invisible to cargo-add consumers (varve pinned 0.9.0). Publish must be gated (dry-run + verify) so a stale registry can no longer diverge from a tagged release." tags: [release, crates-io, supply-chain] fields: @@ -648,4 +648,4 @@ artifacts: created-by: ai-assisted model: claude-opus-4-8 timestamp: 2026-08-07T11:40:52Z - release: v0.11.0 + release: v0.10.0