HotLoop Cascade 1.3.0 release notes
What this is
Section titled “What this is”1.3.0 puts the editor in 14 languages: English, Spanish, French, Italian, German, Norwegian Bokmål, Bulgarian, Greek, Korean, Japanese, Vietnamese, Hindi, Simplified Chinese and Arabic. The engine, the workflow file format, the REST API and the MCP server are what they were in 1.2.1.
The languages
Section titled “The languages”- A language picker sits in the top bar of the editor and on the sign-in page. The choice is kept in the browser, and a first visit follows the browser’s language.
- Every screen is translated: workflows, runs, insights, variables, credentials, projects, users, roles, the audit log, settings, your account, secrets, log streaming and the step editor. So are the step titles and their help, the credential types, and the refusals the server sends when a save, a delete or a sign-in is turned down.
- Dates, numbers, durations and lists come from the browser’s own formatting for the language you picked. Arabic is written right to left, with the canvas, the code and the expressions still left to right. Arabic uses the digits 0 to 9 and the Gregorian calendar.
- Product names, node names, protocol names and example values stay in English in every language. A message about how the person who runs the instance set up a directory, a SAML or OpenID provider, a secret store or a key file is shown as the server wrote it, because the operator searches for that text.
- The words come from the shared HotLoop glossary. The lines a native reader should confirm first are listed in each language’s
_review.json, underweb/src/i18n/locales. Nobody who reads these languages natively has reviewed them yet. - A language is offered only when every line of it is there. The build checks that every language has every English key, that placeholders and tags survive, and that plural forms are right. A Go test keeps the English step words and server messages equal to what the server can say, so a new step or refusal can’t ship without a line to translate.
Also in this release
Section titled “Also in this release”- The editor test that checks the built files never point at another host now allows four example addresses (
https://ntfy.sh,https://example.com,https://hotloop.plantandhttp://hotloop:8080). They appear in step help text, which now ships inside the editor for every language, and they are words in a sentence that nothing fetches. The browser test still fails if the editor requests anything from another host. - The test browser has the Noto fonts for Korean, Japanese, Chinese and Hindi, so those screens draw letters and not empty boxes.
- The OpenBao test helper tries a write again while OpenBao says a new key-value mount is still upgrading (26e1e13).
- HotLoop LLC is named as Cascade’s licensor and maintainer (0ea9cd5).
amd64 only, and why
Section titled “amd64 only, and why”This release builds amd64 only. Multi-arch ships in its own run, so the release after this one is a single small version bump that builds both. stable, latest, 1.3 and 1 list the new amd64 image beside the arm64 image they already pointed at.
A known issue
Section titled “A known issue”In the split install (server, worker and webhook pods on PostgreSQL), the pods start before the database’s name resolves and restart two or three times before they are ready. They come up and the install passes, but it is noisy. 1.2.1 does the same, so this is not new. The fix is to connect with a retry until the database is ready, and it ships in the next release.
Upgrading, and going back
Section titled “Upgrading, and going back”No migrations. helm upgrade to 1.3.0, or let :stable roll the Quadlet units. Putting 1.2.1 back is safe, because nothing in the database changed. The picked language lives in the browser, so going back loses nothing but the picker.