0xDocs 0x.limo

Docs / Reference

Versioning and compatibility

How the /v1 REST API, the @0xlimo/* packages, the 0x CLI and hosted site versions change over time, and what 0x promises about breaking changes.

0x launched on 2026-10-10. Some of what follows is a written promise; the rest is current practice, marked as such, until a formal policy replaces it.

#REST API /v1

  • Every route lives under /v1. The contract is the OpenAPI document of the backend (openapi.yaml, version 1.0), and the API reference is generated from it. A contract test checks that every route the backend serves is documented, and that every documented route exists.
  • Additive changes happen without notice. New routes, new optional request fields and new response fields can appear at any time. Unknown request fields are tolerated, so clients must ignore response fields they don't know.
  • Breaking changes to a /v1 route, such as removing a route or field, changing a field's type or making an optional field required, are not made in place. Current practice: when a flow must change, the old one is kept and marked deprecated in the reference (for example POST /v1/auth/verify_any, the deprecated connect flow), and new behaviour comes as a new route. A future /v2 would run alongside /v1.
  • Switched-off features answer 404 until they are switched on. Switching a feature on is not a breaking change. Build so that a 404 from a switched-off feature degrades gracefully.

#SDK packages @0xlimo/*

  • They are published to the 0x registry (https://0x.limo/npm/), not to npmjs, and follow semver. All of them are in the 0.x range today: current practice is that a patch release (0.1.x) never removes or renames an export, while a minor release (0.x.0) may, and its changelog entry says so.
  • Published versions are never overwritten or removed, so a version you pin keeps installing. Pin exact versions in production games.
  • The 0x CLI depends on exact versions of the packages it bundles into sites (@0xlimo/swarm-sw, @0xlimo/net, @0xlimo/iap, @0xlimo/byo-assets).

#0x CLI

  • The latest version is in the registry's latest tag. The installer installs it into ~/.0x:

    bash
    curl -fsSL https://0x.limo/sdk/install.sh | sh                 # latest
    curl -fsSL https://0x.limo/sdk/install.sh | ZEROX_VERSION=0.1.4 sh  # a pinned version

    Run the installer again to update. The CLI doesn't update itself.

  • Site versions published with an older CLI keep working: each version carries the runtime it was built with (below).

#Hosted site versions

  • Every publish creates a new immutable version at https://<site>-play.0x.limo/sites/<site>/<n>/. Its files never change. The 0x runtime that was added to it at finalize is versioned with it, so a new SDK release never changes a version that is already published.
  • What can change for a published version without a new publish: the response headers 0x serves it with (its security policy, which you control with csp in 0x.config.json; see Security), and swarm delivery (on, private or off).
  • Old shared URLs (https://play.0x.limo/sites/<site>/…) redirect permanently to the site's own origin.

#Steamworks compatibility

The Steam-compatible layer implements specific interface versions (for example SteamUser023), each matched by its exact version string. Current practice: support for an interface version isn't removed; newer versions are added beside the old ones. See Steamworks compatibility.

#Deprecation notices

Deprecations and every developer-visible change are listed in the changelog, with their dates.