Signed files keep their signature a string for every YAML parser #4
Reference in New Issue
Block a user
Delete Branch "bump-library-quoted-signature"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Saved Markdown now carries its signature double-quoted,
signature: "0x…", because YAML reads a bare0x…value as an integer and Memona's frontmatter bar would show a number instead of the hex. The md-ens-signature library is pinned to its current main, which writes the quotes and also brings the ENSv2 owner lookup andverifythat reads will use next.Verified: the wasm32-wasip2 release build, clippy with warnings denied, rustfmt, and twelve unit tests, one of them now checking the quoted signature. Library change: https://github.com/capsulizers/md-ens-signature/pull/20
🤖 Generated with Claude Code
@bot please review the head; it only moves the pinned md-ens-signature revision to current main, so check the lockfile change and the new quoted-signature assertion.
✅ Approved
Summary: The pin matches upstream main; the lockfile resolves and quoted signatures are covered.
Strengths
Dependency and regression coverage
Cargo.tomlandCargo.lockconsistently pinmd-ens-signatureat86878b144154c894948c595d2f0d66fbbd36ae4b, the current upstreammain.signatureas a double-quoted0x...scalar, then parses and recovers it successfully.Issues
None
Recommendations
None
Assessment
Ready to merge
cargo metadata --locked --no-deps,cargo fmt --check,cargo test --locked --lib,cargo clippy --locked --lib -- -D warnings, andcargo build --locked --release --target wasm32-wasip2passed.Declined to judge
None