Updates

1 min read·Updated 30 Jul 2026

Arble uses semantic versioning. Patch and minor releases are backward compatible; major releases may require documented migration steps.

Updating

SHELL

brew upgrade arble          # macOS
arble server migrate        # apply any schema changes first

Pinning a version

In production, pin the exact patch version and upgrade deliberately. An automated install that resolves latest will eventually pick up a change you did not schedule.

What stays compatible

Change	Ships in
New field, endpoint, event or enum value	Any release, without notice
New optional parameter	Patch or minor
Removed or retyped required field	Major only
Changed default behaviour	Major only

Treat unknown fields and unrecognized enum values as forward-compatible. A client that rejects them will break on a routine release.

Disabling update checks

Air-gapped deployments should turn the check off rather than let it time out on every start.

YAML

updates:
  check: false