The Releases screen
See which languages are ready to ship, publish them to the CDN, and copy the setup snippets for your app and pipeline.
Releases is the project page that gets translations out of transglot and into your product. Open it from the project's sidebar. Everyone who can open the project can read it; publishing needs the Admin role or an account Owner, and a plan that includes runtime delivery (Starter and above).
The page has two views, switched with the tabs under the title: Releases for the release work, and Connect & SDK for the setup snippets.
The Releases view
The banners
Above the tables, a banner states where the project stands:
| Banner | What it means |
|---|---|
| "N locales are not ready to publish" | At least one language still has something outstanding. Each row of the table says what. |
| "N locales have strings that need checking" | Some strings carry a review flag. A flag does not stop a publish, so flagged strings go to your website as they stand. Read them opens the flagged strings in the editor. |
| "Every locale is ready to publish" | Every target language would publish complete, and nothing is flagged. |
If your role could publish but your plan cannot, a notice reads "Runtime publishing unlocks on the Starter plan." Readiness and the release log still work on every plan.
Departures
Departures has one row per target language. The source language is not listed: you never ship the source to itself. Each row shows:
| Column | What it shows |
|---|---|
| Locale | The language. |
| Coverage | How much of the language is written, against the project's source strings. |
| Approved | How many strings someone has approved. |
| Needs checking | How many strings carry a review flag. |
| Status | One of the five states below. |
| Live | The version your app is being served, and when it was published. |
| Next | The one action that moves the row forward. |
The Status column uses five words:
| Status | Meaning | Next |
|---|---|---|
| not translated | Nothing is written yet (or the project has no source strings). | translate |
| in progress | Some strings are written, not all. | translate |
| waiting for approval | Everything is written, but this project holds AI drafts back from publishing and some strings are still drafts. | approve |
| ready to publish | Everything that would go into a release is written. | publish (or review if strings are flagged) |
| published | Ready, and a version is already live. | publish to release again |
Whether AI drafts count towards a release is a project setting. See Drafts.
The release card
The card beside the table puts one language forward. It prefers a language that has never been published, and it skips languages with flagged strings. It reads, for example, "German is ready to publish" with the next version number, or "German is live at v3" for a language already being served. When nothing can be offered it says why: No source strings yet, No target languages yet, or No locale is ready to publish, with a link to fix it.
If you cannot publish, the card says so in place of the button: "A workspace admin publishes runtime versions." or "Not available on this account’s plan."
The same language is offered in the page header as Publish German →. See Publish a locale.
This release
A summary of the project's delivery:
- Publishing mode: manual, or on every push. Shown to Owners and Admins.
- Delivered as: the file format the CDN serves. Shown to Owners and Admins.
- Locales live: how many target languages have a published version.
- Last release: when the most recent version was published.
- Never published: how much written work has not reached your app yet.
- Drafts: whether AI drafts go into a release, with Change for the people allowed to set it.
Publishing mode and format are set in Settings → Developer. See The CDN.
Release log
Release log lists the ten most recent publishes, newest first: the language and version, when it was published, how many keys it holds, its format, who published it (system for a publish made through the API or by a push), and a short content fingerprint. Two versions with the same fingerprint hold the same content. Before anything is published it reads "No runtime versions published yet."
The Connect & SDK view
The setup half of the page. Every snippet is pre-filled with this project's real API address, and with a real credential right after you create one.
| Section | What it gives you |
|---|---|
| Connect & verify | Whether the project has a deploy token yet, with a link to the project's setup steps. |
| One provider | A React snippet that adds the in-context editor for your reviewers, pre-filled with the project's publishable key. See Connect the in-context editor. |
| Command line (CLI) | A transglot.json config file and the terminal commands to push your source strings and pull translations back. See CLI. |
| GitHub Action | A workflow file for .github/workflows/transglot.yml. See GitHub Action. |
| Tokens, keys, webhooks & CDN | A pointer to Settings → Developer, where credentials and CDN delivery are managed. |
| Token usage | API calls per deploy token over the last 14 days. Owners and Admins only. |
| API playground | Runs read-only API requests against this project. Shown on plans with API access. |
| Event catalog | Every webhook event with an example payload. See Webhook events. |
The CLI, the GitHub Action and the API authenticate with a deploy token, which needs a plan with API access (Starter and above). On the Free plan the page says so and points you to uploading files from the project's setup page instead.