[lmcorbalan]

Summary

No related issue. RUNBOOK.md step 2 of cutting a release: the root package.json's version has to land on main before v0.3.1 is pushed, or consumers install a package whose manifest names a version their pin does not. v0.3.1 ships #177 (reading active contracts through eventFormat) and the action sha pinning from 5b8a3e8; nothing under daml/, versions.env or the SDK moved, so the DAR should carry the same sha256 as v0.3.0.

Changes

• Root package.json and package-lock.json to 0.3.1. No dependency, script or manifest field otherwise changed.

Acceptance criteria

• The version is the tag without its v, and nothing else in either manifest moved.

Test plan

Automated tests

check:deps, a clean npm ci (which runs prepare) and smoke:registry all exit 0; the packed tarball is bootnodedev-canton-token-forge-0.3.1.tgz and installs, serves and shuts down in the scratch consumer.

Manual verification

The version was applied by hand (npm version reformats the compact manifest objects), four lines across the two files. Because release.yml changed since v0.3.0 (pinned action shas), a workflow_dispatch rehearsal of the release workflow was run on main.

Breaking changes

None.

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

None.