Releases and support

The SDK directory lists the released distribution method for each runtime. Pin the version you test. JavaScript, React Native, and Expo currently install from GitHub release tarballs; Flutter uses a Git dependency. Do not assume similarly named registry packages are official.

Upgrade an SDK

Read that SDK repository's release notes, update the pinned version, and run your application's tests. Recheck consent persistence, link listeners, event IDs, offline retry, and platform associations. For native apps, test the actual signed build you distribute.

A documentation change does not mean a new SDK binary has been released. Compare the release tag and artifact in the relevant repository. Public documentation follows the current service and listed SDK releases; older versions can differ.

Documentation source

The website and linkrunway-docs repository publish the same integration guides. The SDK reference chapters are generated from the maintained SDK guides and release catalog. Report an incorrect field, broken example, or missing step with the page URL and a sanitized reproduction.

Public documentation contributions can be proposed in the documentation repository. Changes are reviewed and reconciled into the website's canonical source before the next publication.

Get help

Email support@linkrunway.com. Include runtime, SDK version, route, HTTP status, timestamp, and steps to reproduce. For public SDK issues, use the relevant SDK repository. Keep security reports private.

Never attach an API key, MCP token, webhook secret, session cookie, database export, or customer payment information. Replace private values with consistent placeholders so the issue remains reproducible.

Service and billing questions

Use the console for current workspace usage, plan entitlements, billing, and team access. See plans and pricing for product information. Documentation does not override your plan, service terms, or account permissions.