`@mushi-mushi/*` upgrades

Hours Low risk

Most packages are already on 1.x. @mushi-mushi/core and @mushi-mushi/web are on 1.23.x; react 1.21.x; vue / svelte / angular / node / capacitor on 1.x. Mobile tracks remain independent (react-native 0.20.x, native iOS/Android 0.4.x). Use each package’s CHANGELOG and npx mushi-mushi upgrade for mechanical bumps.

What stays stable

We expect upgrades within the documented public API to not break:

The Mushi.init({ projectId, apiKey }) shape — this is the public contract every customer wires.
The Mushi.report({ description, ... }) shape.
The <MushiProvider> component in React (and framework equivalents).
Wire-format API endpoints (/v1/reports, /v1/admin/*).
The MCP server protocol.

Possible churn (check CHANGELOG before bumping):

Internal capture types exported via @mushi-mushi/core.
Legacy Mushi.captureException shims.
Bundled-CSS export paths and default privacy-redaction lists.

If you build only against the documented public API (everything under /sdks/* in these docs), most upgrades are a single bump in package.json.

Migration checklist

7 required steps

Step 01
Read the package changelog for every Mushi SDK you use
Step 02
Pin your current versions before upgrading
Step 03
Run the upgrade helper
Step 04
Review the diff
Step 05
Rebuild + run your test suite
Step 06
Smoke-test on a real device / browser
Step 07
Roll out to production behind a canary

Current package tracks (workspace snapshot)

Package	Current track
`@mushi-mushi/core` / `web`	1.23.x
`@mushi-mushi/react`	1.21.x
`@mushi-mushi/vue` / `svelte` / `angular`	1.0.x
`@mushi-mushi/node` / `capacitor`	1.1.x
`@mushi-mushi/react-native`	0.20.x
`@mushi-mushi/cli`	0.26.x
`@mushi-mushi/mcp`	0.19.x
iOS / Android native	0.4.x

See the SDK index version matrix for the live workspace snapshot.

@mushi-mushi/* upgrades

What stays stable

Migration checklist

Current package tracks (workspace snapshot)

`@mushi-mushi/*` upgrades