From 4abb04605a62e2b9d7607bcbf4a8cb51b420ee40 Mon Sep 17 00:00:00 2001 From: aterga Date: Thu, 24 Sep 2026 15:36:23 +0000 Subject: [PATCH] Describe the pre-scheme local releases by their tag, not by a version The install note said releases "before 0.6.0" predate the candidate flow, assuming 0.6.0 would be the first version cut under it. The crates were bumped to 0.5.1 and tagged in the meantime, so the boundary is not a version number; what identifies the older releases is their imcp2-local-vX.Y.Z tag and the workflow name that attested them, which is what the note now says. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01Xd7VT72Qt16qiAJynu9EKj --- crates/imcp2-local/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/crates/imcp2-local/README.md b/crates/imcp2-local/README.md index 38425c2..deedb86 100644 --- a/crates/imcp2-local/README.md +++ b/crates/imcp2-local/README.md @@ -47,11 +47,11 @@ curl -fLO "https://github.com/dfinity/imcp2/releases/download/$TAG/imcp2-local-$ two commands create it and copy the binary there, nothing edits your shell configuration. -Releases before 0.6.0 predate this scheme: they are tagged `imcp2-local-vX.Y.Z` -(the newest is `imcp2-local-v0.5.0`), are not what `latest` resolves to, and -their archives were attested by `imcp2-local-release.yml`, the workflow's name -at the time. To install one of those, set `TAG` to its tag and pass that -filename to `--signer-workflow`; everything else above is the same. +Releases tagged `imcp2-local-vX.Y.Z` predate this scheme: they are not what +`latest` resolves to, and their archives were attested by +`imcp2-local-release.yml`, the workflow's name at the time. To install one of +those, set `TAG` to its tag and pass that filename to `--signer-workflow`; +everything else above is the same. (Windows ships `imcp2-local-x86_64-pc-windows-msvc.zip`; verify it the same way.)