chore: bump manifests to next dev versions after 1.11.0

[insipx]

Answers "do we need to PR the version bump" — yes. The 1.11.0 reconcile squash (#3922) left main's manifests at the released versions, but compute-version bases dev builds on the manifest: the next dev publish would emit 1.11.0-dev.<sha>, which semver-sorts below the released 1.11.0 and would drag the npm dev dist-tag backwards.

Precedent: the 1.10.0 reconcile (#3327) included this bump (1.10.0 → 1.11.0-dev) in the same commit; the pipeline-generated reconcile doesn't do that — one more for the pipeline-gaps list (create-release-branch/merge flow should append the next-dev bump).

Applied with the release tooling (xmtp-release set-manifest-version), next-minor -dev per track:

track	version
libxmtp / node-bindings / wasm-bindings	1.12.0-dev
node-sdk	6.2.0-dev
browser-sdk	7.2.0-dev
iOS / Android	4.12.0-dev

Cargo.lock refreshed by the tool; verified with cargo metadata --locked --offline. (If the next release turns out patch-only, create-release-branch re-bakes the real versions at branch time — the manifest is the dev baseline, same as last cycle.)

🤖 Generated with Claude Code

Note

Bump all package manifests to 1.12.0-dev after 1.11.0 release

Advances version numbers across all SDK and binding manifests to the next development cycle. Updates cover Cargo.toml, bindings/node/package.json, bindings/wasm/package.json, the Android, iOS, and JS SDKs.

^{Macroscope summarized 5071d0e.}

[claude]

Claude finished @insipx's task —— View job

---

PR Review — 2026-07-29 16:51 UTC

• Read and analyze changed files
• Verify version consistency across platforms
• Check for potential issues
• Provide review feedback

---

Review Feedback

This version bump PR is well-executed and necessary. The rationale is clear: without bumping to -dev versions, the next dev publish would sort below the released version.

✅ Strengths

1. Version consistency — All version bumps follow the correct next-minor pattern:

   • Cargo.toml:29 — 1.12.0-dev ✓
   • bindings/node/package.json:3 — 1.12.0-dev ✓
   • bindings/wasm/package.json:3 — 1.12.0-dev ✓
   • sdks/js/node-sdk/package.json:3 — 6.2.0-dev ✓
   • sdks/js/browser-sdk/package.json:3 — 7.2.0-dev ✓
   • sdks/ios/XMTP.podspec:3 — 4.12.0-dev ✓
   • sdks/android/gradle.properties:26 — 4.12.0-dev ✓

2. Cargo.lock properly refreshed — The lockfile was updated by the tooling and verified with cargo metadata --locked --offline

3. Correct semver strategy — Using -dev suffix prevents semver sorting issues where 1.11.0-dev.<sha> would sort below 1.11.0

No issues found

• No code quality concerns
• No bugs or security issues
• No performance considerations
• No test coverage needed (version manifest changes only)

The PR correctly addresses a gap in the automated reconcile pipeline that should be documented for future process improvements.

---

[macroscopeapp]

Approvability

Verdict: Approved 5071d0e

Version string bumps in manifest files (Cargo.toml, XMTP.podspec) after a release. No runtime behavior changes, and the author owns both files.

^{You can customize Macroscope's approvability policy. Learn more.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.83%. Comparing base (cf3b084) to head (5071d0e).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3923      +/-   ##
==========================================
+ Coverage   85.81%   85.83%   +0.02%     
==========================================
  Files         416      416              
  Lines       68175    68175              
==========================================
+ Hits        58507    58521      +14     
+ Misses       9668     9654      -14     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.