chore: release v0.0.14

[bullet-release]

🤖 New release

• bullet-rust-sdk: 0.0.13 -> 0.0.14

Changelog

0.0.14 - 2026-05-11

Features

• (ci) Add Release Pipeline (NPM) (#13)

---

This PR was generated with release-plz.

---

Note

Low Risk
Low risk release bookkeeping: version/changelog/lockfile updates plus a formatting-only change to wasm/package.json. No runtime logic changes in the SDK are included.

Overview
Cuts release 0.0.14 by bumping bullet-rust-sdk version (rust/Cargo.toml and Cargo.lock) and adding the corresponding rust/CHANGELOG.md entry (noting the CI/NPM release pipeline feature).

Also normalizes wasm/package.json by adding the missing trailing newline (no functional JS/WASM package changes).

^{Reviewed by Cursor Bugbot for commit 713938e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cubic-dev-ai]

No issues found across 2 files

_{Tip: cubic could auto-approve low-risk PRs like this, if it thinks it's safe to merge. Learn more}

[Firaenix]

Need this to be retriggered with JS package bump

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 713938e. Configure here.}

[cursor]

WASM package version not bumped in lockstep

High Severity

The Rust SDK version is bumped to 0.0.14 but wasm/package.json (and wasm/Cargo.toml) remain at 0.0.13. The release-plz.toml config explicitly states the wasm crate version is bumped in lockstep with the Rust crate and that npm publish is driven from the same v0.0.14 tag. Publishing from the v0.0.14 git tag with package.json still at 0.0.13 will result in the wrong version being published to NPM, or a version mismatch between the git tag and the published artifact.

Additional Locations (1)

• wasm/package.json#L74-L79

 

^{Reviewed by Cursor Bugbot for commit 713938e. Configure here.}