Releases and upgrades

Match documentation to your SDK version and plan database or extension upgrades.

Oliphaunt SDKs and runtimes have independent versions. Use the version table to see the package versions documented by this site, and the package's linked release notes for changes.

Match your dependency

Install examples use the versions associated with this documentation build. Pin dependencies in your package manifest or lockfile so an application rebuild uses the versions you tested.

The SDK package selects compatible runtime dependencies. Keep those dependencies together instead of independently replacing a native library, WebAssembly runtime, or helper executable. React Native also depends on compatible Swift and Kotlin integrations.

Extension packages have their own versions and runtime compatibility. A matching numeric version across unrelated products is not a compatibility guarantee.

Upgrade an application

  1. Read release notes for your SDK, its runtime changes, and selected extensions.
  2. Create a recoverable backup and test the upgrade against a copy of application data.
  3. Update the application dependency and its lockfile.
  4. Rebuild native applications when runtime resources or extensions change.
  5. Apply documented schema or extension migrations.
  6. Verify queries, transactions, restart recovery, and restore before switching user data.

Use physical restore only when runtime-family and format compatibility are documented. Use logical dump/restore for incompatible formats or transfers between native and WASIX. See WASIX dump and restore for an example.

Find the matching reference

Use Versions to compare your dependencies with this documentation. For an older SDK, open its release tag to read the README shipped with that version. When reporting a docs issue, include your SDK version and the page URL.

See all GitHub releases for release notes and downloadable artifacts.