fix(deps): bump react-native-mmkv from 3.3.3 to 4.0.1

[dependabot]

Bumps react-native-mmkv from 3.3.3 to 4.0.1.

Release notes

Sourced from react-native-mmkv's releases.

Release 4.0.1

4.0.1 (2025-11-18)

✨ Features

• Add MMKV.id (#953) (5d8eb56)

🐛 Bug Fixes

• Fix build step in actions (#949) (c870593)
• Fix incorrect return of remove on Web (#957) (4fc2863)
• Upgrade to Nitro 0.31.7 (27e69df)

📚 Documentation

• Replace Flipper with Rozenite for MMKV debugging (#950) (d9e58b3)

Release 4.0.0

4.0.0 (2025-10-20)

react-native-mmkv V4 is the next major evolution of the library - it features:

• A full rewrite to Nitro! 🔥
  • ..this implies that V4 now works again on the old-architecture, until react-native 0.82 at least.
• react-native-mmkv V4 now uses MMKVCore from CocoaPods/Gradle instead of shipping it as source - this means you can use the native MMKV library from your native code again without causing duplicate symbols!
• Make set(...) throw a useful Error when the value couldn't be saved
• Adds useMMKVKeys()
• Make remove(...) return a bool
• Add AppGroup again
• Make remove(...) and clearAllKeys() invoke listeners properly

‼️ Before upgrading, please read the V4 upgrade guide. ‼️

✨ Features

• add React Native Harness (#918) (cbcb4bd)
• Throw if set(...) was not successful (#921) (0d3b833)
• Upgrade MMKVCore to 2.2.4 (Android) (#912) (cf77676)
• Upgrade Nitro to 0.30.0 (#923) (03dd7c9)
• Upgrade to Nitro 0.31 (#929) (176e4f3)
• Upgrade to react-native 0.82.0 (#930) (5f7d595)

🐛 Bug Fixes

• Fix example app build for Xcode 26 (#922) (965a549)
• Notify listeners when keys get removed (remove/clearAll) (#920) (09643c3)
• Throw if key is empty in set(...) (#919) (3d3b793)

Release 4.0.0-beta.12

4.0.0-beta.12 (2025-09-26)

... (truncated)

Commits

• 39f29c2 chore: release 4.0.1
• 27e69df fix: Upgrade to Nitro 0.31.7
• 4fc2863 fix: Fix incorrect return of remove on Web (#957)
• d9e58b3 docs: Replace Flipper with Rozenite for MMKV debugging (#950)
• 5d8eb56 feat: Add MMKV.id (#953)
• c870593 fix: Fix build step in actions (#949)
• e559aa5 chore: Run build at top level
• fa1de4f chore: move postinstall script (#939)
• 890afed chore: Swap READMEs
• 81d5e25 chore: Update lockfiles
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.