Migration Guides
Migration guides
Upgrade Lucid runtime and x402 integrations without mixing release channels.
Read the release channel contract before an upgrade. Stable describes clean-room-tested public npm artifacts; Next describes the current repository surface.
Lucid runtime v3 (Next)
Adopt extension-owned runtime slices, the canonical registry, and shared HTTP authorization.
x402 v2
Move from legacy unscoped dependencies and headers to scoped x402 v2 packages and CAIP-2 networks.
Before changing production dependencies, reproduce the target version in a clean project and run the paid seller/buyer transaction. Do not infer npm availability from a package version in the repository.
For defects or ambiguous behavior, include the exact Lucid and x402 package versions in a GitHub issue.