Release request: publish 1.13.x to npm (repo is at 1.13.2, npm latest is still 1.10.3) #15

Hi! Thanks for upgrading the binding to loro-ffi 1.13.1 (#13) and 1.13.2 (#14) — much appreciated.

It looks like these upgrades were never published: npm's latest dist-tag still points at 1.10.3, and no 1.13.x version appears in npm view loro-react-native versions.

Would you be able to cut an npm release of 1.13.2? We run loro-crdt@1.13.x on web and the official RN binding on mobile, and consuming the published 1.10.3 means carrying a TS-side port of the >=1.13 mergeable-container semantics to keep cross-binding parity — a published 1.13.2 would let us retire that shim and track the native core directly.

Happy to help test a release candidate against our cross-binding contract corpus (byte-identical update exports across wasm and native) if useful.