The Unity package is the unit of release. It bundles a compatible native binary and the matching @loomgui/bridge and @loomgui/vite-plugin packages. Loom -> Sync UI Dependencies installs them into your UI app. There are no versions to reconcile by hand; the npm packages ship with the package you installed. See the in-repo CHANGELOG.md at the root of the project for the full per-release log.

Upgrading

v0.1.x → v0.2.x is a breaking upgrade with two source changes: your [Bridge] class now inherits LoomBridgeBase and the hand-written bootstrap is replaced by the LoomUI component, and bridge state moves from Observable<T> to plain { get; set; } properties (with ReactiveList<T> / ReactiveMap<K,V> for collections). Updating the package itself is a single step. Follow the v0.1 → v0.2 migration guide.

Versioning policy

• Patch (0.1.0 -> 0.1.1). Bug fixes only. No bridge surface changes, no breaking changes. Safe to drop in.
• Minor (0.1.x -> 0.2.0). New features. May include a breaking native protocol change that requires reinstalling the Unity package. Source-compatible.
• Major (0.x -> 1.0). Breaking source changes (member-attribute renames, protocol overhaul).

Pre-1.0 versions may break source compatibility on minor bumps. Once 1.0 ships, semantic versioning is strict.