Skip to content

Vendor @sidestr/spec 0.0.6: records read by push length; 0.0.11 - #32

Merged
jjohare merged 1 commit into
JavaScriptSolidServer:mainfrom
jjohare:chore/vendor-spec-0.0.6
Sep 25, 2026
Merged

jjohare merged 1 commit into
JavaScriptSolidServer:mainfrom
jjohare:chore/vendor-spec-0.0.6

Conversation

@jjohare

@jjohare jjohare commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

The vendored spec lib moves from 373d3eb to @sidestr/spec 0.0.6 (fa86dac), which includes the records fix from sidestr/spec#17. 0.0.11.

  • The bug: recordText's push-length check had slipped behind a comment, so a script that pushed tal with ly:x trailing after the push read as the record tally:x.
  • Effect here: Podkey's spend window reads asset records through this function, so it now reads them exactly as validators do.
  • What changed: only records.mjs changes in Podkey's vendored set. The explorer (db5a04e) and schema (v0.0.27) are unchanged, and PINS.json records the new hashes.
  • Test: a new test holds the vendored reader to the fix.

npm test passes 229/229, lint is clean, and the build succeeds.

🤖 Generated by Claude Code

…s push length; 0.0.11

sidestr/spec#17: recordText's length check had slipped behind a comment, so a
script pushing 'tal' with 'ly:x' after the push read as the record 'tally:x'.
Only records.mjs changes in Podkey's vendored set; a test holds the vendored
reader to the fix.

Co-Authored-By: jjohare <github@thedreamlab.uk>
@jjohare
jjohare merged commit 3752aa2 into JavaScriptSolidServer:main Sep 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant