How do I use Localazy CLI with Releases?

Release Tags let you control exactly which version of translations gets served to users in each environment, independent of what translators are actively working on.

By default, every change published in Localazy becomes part of the latest tag automatically, updated within 15-minute intervals. This is useful during development, but in production you typically don’t want live translator edits to reach users immediately. Release Tags solve this by creating a named snapshot of your project’s current translation state.

# Publish current translations as a staging release
localazy tag publish staging

# When ready, promote staging to production
localazy tag promote staging production

# Or tag a specific version
localazy tag promote staging v2.1

Once a tag is published, its content stays fixed unless you explicitly update it. Translators can continue working, and new strings can be added without affecting what production serves. When you’re confident in the new state, promote staging to production with a single command.

In a CI/CD pipeline, the pattern works like this: your upload step pushes new source strings to Localazy on merge; translators translate in the dashboard; your release pipeline downloads using the -t flag to pull a specific tag, then promotes it if tests pass.

# Download translations pinned to the production tag
localazy download -t production

This gives you a clean separation between “translations being worked on” and “translations shipped to users,” with no manual file management involved.