fix(v1.0.1): correct SCRY_VERSION self-report 0.9.0 → 1.0.1#26
Merged
Conversation
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 <version> — 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) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v1.0.1 — patch: correct
SCRY_VERSIONself-reportThe
analyze()diagnostic banner ("scry <version> — wasm-latticecross-component import alive") hard-codes
SCRY_VERSION, which was leftat
"0.9.0"when v1.0.0 shipped — the version-bump edit did not land inthe v1.0.0 PR (#25).
Impact: the constant feeds only an
Info-level diagnostic string. Nosoundness, 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.0is the kind of provenance mismatch scry exists to catch, so thispatch corrects it to
"1.0.1".Falsifiable kill-criterion: the
SCRY_VERSIONconstant and therelease tag agree. Verified locally:
bazel build //:scrygreen +wasm-tools validateok.🤖 Generated with Claude Code