> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/moss-docs/wallet/versioning.md).

# Changelog and Versioning

Current published package versions (npm `latest`):

* `@megaeth-labs/wallet-sdk`: `0.1.27`
* `@megaeth-labs/wallet-sdk-react`: `0.1.26`
* `@megaeth-labs/wallet-server-verify`: `0.1.9`
* `@megaeth-labs/wallet-wagmi-connector`: `0.3.1`

## Compatibility Notes

* The React SDK currently depends on the core SDK at `0.1.26`.
* The React SDK expects `react@^19` and `@tanstack/react-query@^5`.
* Wallet packages currently publish as ESM and CJS bundles with type declarations.
* The server verification package depends on `viem` and `porto` and is intended for backend use, not browser bundles.

## What Changed in This Docs Pass

* Documented newly covered APIs across Web + React references:
  * `signData`
  * `balances`
  * `getPermissions(address?)`
  * `deposit`
  * `open`
* Added coverage for newly exported core methods:
  * `send`
  * `swap`
* Added `@megaeth-labs/wallet-wagmi-connector` docs and integration notes for plain wagmi, RainbowKit, ConnectKit, and Reown AppKit.
* Clarified session/permissions flow with canonical call matcher guidance.
* Updated lifecycle + initialization docs to reflect iframe + Penpal behavior and current return signatures.
* Expanded React wrapper coverage, including React Query requirements and the `mega` re-export.

## Release Guidance for Partners

* Pin tested versions in production integrations instead of floating to the newest release automatically.
* Re-run sign, transfer, permissions, and contract-call smoke tests whenever either package version changes.
* Treat wallet host behavior and query-param based config as release-sensitive integration points.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.megaeth.com/moss-docs/wallet/versioning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.