Breaking Updates

Companion Hub has no breaking version-to-version updates to document yet. This page will be updated as major changes occur. For the routine update process, see Updating Companion Hub.

Backward compatibility with legacy naming

Companion Hub builds on the foundation of the RunTipi self-hosting platform, so a number of legacy names are still accepted for compatibility. You do not need to change anything for these to keep working, but new apps and configurations should use the current names.

App manifest fields (`config.json`)

Legacy field	Current field	Notes
`tipi_version`	`cihub_app_version`	Manifest revision number. Prefer the current name for new apps.
`min_tipi_version`	`min_hub_version`	Minimum Hub version required by the app.

Both legacy fields are still parsed and mapped automatically. See config.json options for the full manifest format.

Environment variables

Earlier TIPI_* and RUNTIPI_* environment variables are mapped to their CI_HUB_* equivalents at startup. The version variable, for example, is now CI_HUB_VERSION (there is no TIPI_VERSION). See Environment variables for the current list, including a table of legacy variables still accepted.

Local domain

Hub no longer hardcodes a LAN domain. LOCAL_DOMAIN now resolves to your configured DOMAIN when unset, and to localhost when neither is set — so apps are reachable at <app-name>.localhost out of the box, with no DNS configuration.

If you set a custom localDomain previously, it is preserved and still takes precedence. Installations that relied on the former ci.lan default should set LOCAL_DOMAIN explicitly to keep their existing hostnames working.

See Finding Your App’s URL and Custom settings.

Legacy names are a compatibility convenience, not a long-term guarantee. New installations and app submissions should use the current cihub_app_version, min_hub_version, and CI_HUB_* names.