From cf9b03205a471bb4ad8f6acfb31735b404528d61 Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Sat, 30 May 2026 06:14:31 +0200 Subject: [PATCH] fix(v1.0.1): correct SCRY_VERSION self-report from 0.9.0 to 1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The analyze() diagnostic banner hard-codes SCRY_VERSION, which was left at "0.9.0" when v1.0.0 shipped — the version-bump edit did not land in the v1.0.0 PR (#25). The constant feeds only an Info-level diagnostic string ("scry — wasm-lattice cross-component import alive"); no soundness, invariant, or analysis behaviour was affected and the v1.0.0 artifact is otherwise correct. But a v1.0.0 component that self-reports 0.9.0 is exactly the provenance mismatch scry exists to catch, so this patch corrects it. Verified: bazel build //:scry green + wasm-tools validate ok. Co-Authored-By: Claude Opus 4.8 (1M context) --- CHANGELOG.md | 24 +++++++++++++++++++++++- crates/scry-analyzer/src/lib.rs | 2 +- 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 9e2f048..a86f1fe 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,27 @@ Versioning: [SemVer 2.0](https://semver.org/spec/v2.0.0.html). ## [Unreleased] +## [1.0.1] — 2026-05-30 + +### Fixed + +- **`SCRY_VERSION` self-report corrected to the shipped version.** The + `analyze()` diagnostic banner ("scry <version> — wasm-lattice + cross-component import alive") hard-codes `SCRY_VERSION`, which was left + at `"0.9.0"` when v1.0.0 shipped (the version-bump edit did not land in + the v1.0.0 PR). The constant feeds only an `Info`-level diagnostic + string — no soundness, invariant, or analysis behaviour was affected, + and the v1.0.0 artifact is otherwise correct — but a v1.0.0 component + that self-reports `0.9.0` is the kind of provenance mismatch scry + exists to catch, so it is corrected here to `"1.0.1"`. + +### Falsifiable kill-criterion + +`grep 'SCRY_VERSION: &str = "1.0.1"' crates/scry-analyzer/src/lib.rs` +matches, and the released artifact's `analyze()` diagnostic reports the +same version string as the release tag. If the constant and the tag ever +disagree again, this release is wrong. + ## [1.0.0] — 2026-05-29 Headline: **the safety goal closes**. v1.0 is the capstone: the mechanized @@ -818,7 +839,8 @@ falsifier. See git history for pre-v0.1 work (initial scope-out + DD-002 closure in PR #2). -[Unreleased]: https://github.com/pulseengine/scry/compare/v1.0.0...HEAD +[Unreleased]: https://github.com/pulseengine/scry/compare/v1.0.1...HEAD +[1.0.1]: https://github.com/pulseengine/scry/releases/tag/v1.0.1 [1.0.0]: https://github.com/pulseengine/scry/releases/tag/v1.0.0 [0.9.0]: https://github.com/pulseengine/scry/releases/tag/v0.9.0 [0.8.0]: https://github.com/pulseengine/scry/releases/tag/v0.8.0 diff --git a/crates/scry-analyzer/src/lib.rs b/crates/scry-analyzer/src/lib.rs index b0612f9..a4c51dd 100644 --- a/crates/scry-analyzer/src/lib.rs +++ b/crates/scry-analyzer/src/lib.rs @@ -179,7 +179,7 @@ use scry_provenance::ComponentOrigin as ProvOrigin; struct Component; -const SCRY_VERSION: &str = "0.9.0"; +const SCRY_VERSION: &str = "1.0.1"; const INVARIANT_SCHEMA_URL: &str = "https://pulseengine.eu/scry-invariants/v1"; /// Default Wasm linear-memory page size (64 KiB).