Skip to content

js: release bolt12-utils v0.1.2#34

Merged
vincenzopalazzo merged 1 commit into
rustyrussell:masterfrom
vincenzopalazzo:release/js-0.1.2
Jun 26, 2026
Merged

js: release bolt12-utils v0.1.2#34
vincenzopalazzo merged 1 commit into
rustyrussell:masterfrom
vincenzopalazzo:release/js-0.1.2

Conversation

@vincenzopalazzo

Copy link
Copy Markdown
Collaborator

Summary

  • Bump bolt12-utils 0.1.1 -> 0.1.2 (js/package.json, js/package-lock.json).
  • Add js/CHANGELOG.md (Keep a Changelog format).

This is a release-metadata PR for the payer-proof data-range fix that landed in #33. No code changes beyond the version bump and changelog.

Changelog (0.1.2)

Fixed:

  • Payer proof reader excludes the payer-proof data range (1001..=999_999_999) from invoice merkle reconstruction, so an unknown TLV there is no longer mis-counted as an invoice leaf (which wrongly failed the proof_leaf_hashes count). A record is an invoice field only when type < 240 or type >= 1_000_000_000, mirroring rust-lightning's tlv_stream_iter.
  • Reject unknown even TLVs in the data range per the BOLT "it's ok to be odd" rule; unknown odd types remain ignorable and stay committed by proof_signature.

Notes

  • dist/ is gitignored; npm publish regenerates it via prepublishOnly. The actual npm publish will be done after this merges.
  • No tag created here — leaving the v0.1.2 tag / npm publish to the release step.

Test plan

  • npm run build clean
  • npm test — 53 + 36 + 22 + 3 all pass
  • npm pack --dry-run -> bolt12-utils@0.1.2, 52 files, 57.6 kB

Bump version 0.1.1 -> 0.1.2 and add a changelog. This release ships the
payer-proof data-range TLV handling fix (PR rustyrussell#33): the reader excludes the
payer-proof data range (1001..=999_999_999) from invoice merkle
reconstruction and rejects unknown even TLVs in that range per the BOLT
"it's ok to be odd" rule.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vincenzopalazzo vincenzopalazzo merged commit 4167b54 into rustyrussell:master Jun 26, 2026
4 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