chore: prep for 2.0.5 release

[ignaciosantise]

This pull request primarily updates and pins dependency versions across the monorepo and example projects, with a focus on improving compatibility and stability.

Dependency version pinning and updates:

• Pinned peer dependency version ranges for several @reown/appkit-* React Native packages to ensure consistent and predictable installs. (.changeset/cuddly-heads-type.md)

Peer dependency range tightening:

• Tightened peer dependency ranges for @react-native-community/netinfo and react-native-get-random-values in packages/ethers/package.json and packages/wagmi/package.json to require minimum versions, improving compatibility guarantees. [1] [2]

Tooling and dev dependency maintenance:

• Upgraded dev dependencies such as tsconfig and turbo to newer versions in the root package.json, helping maintain build and test tooling.

Overall, these changes help ensure the project uses compatible and up-to-date dependencies, reducing the risk of version conflicts and improving overall stability.

[changeset-bot]

🦋 Changeset detected

Latest commit: c1b28b1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@reown/appkit-react-native	Patch
@reown/appkit-bitcoin-react-native	Patch
@reown/appkit-coinbase-react-native	Patch
@reown/appkit-common-react-native	Patch
@reown/appkit-core-react-native	Patch
@reown/appkit-ethers-react-native	Patch
@reown/appkit-solana-react-native	Patch
@reown/appkit-ui-react-native	Patch
@reown/appkit-wagmi-react-native	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[claude]

Claude finished @ignaciosantise's task in 34s —— View job

---

• Gather context & read changed files
• Spawn license compliance subagent — ✅ No issues found
• Spawn data classification subagent — ✅ No issues found
• Spawn breaking changes subagent — ⚠️ 3 issues found
• Synthesize findings & post final review

---

Found 3 issue(s)

Issue 1: Narrowing netinfo peer dep from * → >=11.0.0 excludes large installed base

ID: brk-ethers-wagmi-peerdep-netinfo-tighten-a3f2
File: packages/ethers/package.json:46, packages/wagmi/package.json:47
Severity: HIGH
Category: breaking_change

Context:

• Pattern: @react-native-community/netinfo minimum raised from * → >=11.0.0, excluding v4.x–v10.x.
• Risk: Consumers on netinfo 4.x–10.x will receive hard peer dep resolution failures. v11.0.0 also introduced a hard Android compileSdk >= 33 requirement, forcing consumers on older build configs to do more than just bump a single dep.
• Impact: Any existing consumer with netinfo < 11.0.0 will be blocked from upgrading to 2.0.5 without additional work.
• Trigger: Any install/upgrade by a consumer with netinfo < 11.0.0 pinned.

Recommendation: If older netinfo versions are genuinely incompatible (runtime failures), document this and ship as minor. If they remain functional, revert to a less aggressive minimum (e.g. >=9.0.0). Either way, see Issue 3 on the changeset type.

---

Issue 2: Changeset marks all packages as patch for a range-narrowing breaking change

ID: brk-changeset-peerdep-semver-mismatch-f5e8
File: .changeset/cuddly-heads-type.md:1
Severity: HIGH
Category: breaking_change

Context:

• Pattern: All 9 packages marked patch for a change that narrows peer dep ranges.
• Risk: Narrowing peer dep minimums is a breaking change under semver — it can cause existing consumer installs to fail. Publishing as patch signals it is safe to auto-apply (Dependabot, Renovate will do so), surfacing peer dep errors in CI for consumers on older versions.
• Impact: Misleading semver metadata for the entire consumer ecosystem.
• Trigger: Any consumer using automated patch-update tooling.

Recommendation: Change patch → minor for at minimum @reown/appkit-ethers-react-native and @reown/appkit-wagmi-react-native. Bumping all nine to minor to keep versions in sync is also acceptable. Add a note in the changeset body listing the new minimum peer dep versions:

'@reown/appkit-ethers-react-native': minor
'@reown/appkit-wagmi-react-native': minor

---

Issue 3: Narrowing get-random-values peer dep from * → >=1.11.0 excludes v1.8–v1.10 without functional necessity

ID: brk-ethers-wagmi-peerdep-rngvalues-tighten-c7d1
File: packages/ethers/package.json:50, packages/wagmi/package.json:52
Severity: MEDIUM
Category: breaking_change

Context:

• Pattern: react-native-get-random-values minimum raised from * → >=1.11.0. The only new capability in v1.11.0 was bridgeless architecture support — it is not a bugfix, so v1.8–v1.10 remain functionally correct for standard (non-bridgeless) use.
• Risk: Consumers not using bridgeless mode on v1.8–v1.10 will get peer dep failures when upgrading, despite no functional incompatibility.
• Impact: Unnecessary friction for non-bridgeless consumers upgrading to 2.0.5.
• Trigger: Peer dep resolution failure on install if react-native-get-random-values is pinned below 1.11.0.

Recommendation: If the library does not depend on bridgeless-specific behavior, use >=1.8.0 or >=1.9.0 instead. If it does, document it in the changeset body and treat as minor.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	metro-react-native-babel-preset@​0.77.0
	@​babel/​plugin-proposal-private-methods@​7.18.6
	@​testing-library/​jest-native@​5.4.3
	eslint@​9.34.0 ⏵ 8.57.1				-44
	@​react-native/​typescript-config@​0.76.7
	@​walletconnect/​react-native-compat@​2.22.2 ⏵ 2.21.5					+20
	@​changesets/​changelog-github@​0.5.1
	jest@​29.7.0
	@​react-native/​metro-config@​0.76.7
	@​babel/​preset-typescript@​7.24.7
	@​babel/​plugin-transform-flow-strip-types@​7.26.5
	@​types/​qrcode@​1.5.5
	tsconfig@​7.0.0
	@​react-native/​eslint-config@​0.76.7
	react-native-builder-bob@​0.40.13
	@​types/​jest@​29.5.7
	@​babel/​preset-env@​7.28.0
	wagmi@​2.15.6
	react-native-safe-area-context@​5.6.1
	@​coinbase/​wallet-mobile-sdk@​1.1.2
	@​types/​react@​19.1.13 ⏵ 18.2.79				+1
	react-native-get-random-values@​1.11.0
	@​babel/​core@​7.28.3 ⏵ 7.26.10			+1
	eslint-plugin-ft-flow@​2.0.3
	react-test-renderer@​18.3.1
	@​types/​node@​24.3.0 ⏵ 22.10.1
	@​react-native/​babel-preset@​0.81.4 ⏵ 0.76.7
	ts-node@​10.9.1
	eslint-plugin-valtio@​0.8.0
	react@​18.3.1
	turbo@​2.9.14
	babel-loader@​9.1.3
	react-native@​0.80.2
See 18 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm react-native is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: apps/native/package.json → npm/react-native@0.76.7 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-native@0.76.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm react-native is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: packages/appkit/package.json → npm/react-native@0.80.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-native@0.80.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report