Freeze a finished language into an immutable runtime version and serve it from the CDN.
Who this is for
Owners and admins, on a plan that includes runtime publishing.
Before you start
The locale has to be completely translated. Publishing a partial locale would ship gaps to production, so the screen does not offer it.
Steps
Open the project's Deploy.
Check Locale readiness: the language you want should show all its strings translated.
In the Ready to ship card, select Publish followed by the language name.
What happens next
Publishing freezes every string in that locale into a new immutable runtime version and serves it from the CDN. Nothing else in the project changes: your live translations carry on being editable, and the published version stays exactly as it was at the moment you published.
The new version appears in Deploy history, and Locale readiness now shows its version number instead of never published.
Because each version is immutable, rolling back is a matter of pointing at an earlier version rather than undoing anything.
If it doesn't work
If the card reads Not ready yet, the locale still has untranslated strings. Open the editor takes you to them.
"No target languages yet": add a language first.
"An organisation admin publishes runtime versions.": you do not have the permission.
"Not available on this organisation's plan.": runtime publishing needs a paid plan. Everything else on the deploy screen still works.
Related
The deploy screen
The CDN
Why are my translations not reaching my app?