Skip to content

The open alternative to Salesforce, designed for AI.

i18n - docs translations (#19490)

github-actions[bot]64c7f52f0667
diff --git a/packages/twenty-docs/l/ar/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/ar/developers/extend/apps/publishing.mdx
index e2ff4a5b28d..d3a86aafb9b 100644
--- a/packages/twenty-docs/l/ar/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/ar/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ yarn twenty deploy
### إدارة الإصدارات
+عند تحديث تطبيق tarball منشور مسبقًا، يشترط الخادم أن تكون قيمة `version` في `package.json` **أعلى قطعًا** (وفق ترتيب [الإصدار الدلالي](https://semver.org)) من الإصدار المنشور حاليًا. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
لطرح تحديث:
-1. ارفع قيمة الحقل `version` في ملف `package.json`
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. شغّل `yarn twenty deploy` (أو `yarn twenty deploy --remote production`)
3. سترى مساحات العمل التي ثبّتت التطبيق الترقية متاحة في إعداداتها
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## النشر على npm
@@ -189,3 +195,12 @@ jobs:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>
diff --git a/packages/twenty-docs/l/cs/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/cs/developers/extend/apps/publishing.mdx
index 646f2047d54..0bdba36168b 100644
--- a/packages/twenty-docs/l/cs/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/cs/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ Odkaz ke sdílení používá základní adresu URL serveru (bez jakékoli subdo
### Správa verzí
+When updating an already deployed tarball app, the server requires the `version` in `package.json` to be **strictly higher** (per [semver](https://semver.org) ordering) than the currently deployed version. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
Chcete-li vydat aktualizaci:
-1. Zvyšte hodnotu pole `version` v souboru `package.json`
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. Spusťte `yarn twenty deploy` (nebo `yarn twenty deploy --remote production`)
3. Pracovní prostory, které mají aplikaci nainstalovanou, uvidí dostupnou aktualizaci ve svém nastavení
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## Publikování na npm
@@ -189,3 +195,12 @@ Aplikace můžete nainstalovat také z příkazového řádku:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>
diff --git a/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx
index 4f00abdfbea..d43e388030c 100644
--- a/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/de/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ Der Freigabelink verwendet die Basis-URL des Servers (ohne Workspace-Subdomain),
### Versionsverwaltung
+When updating an already deployed tarball app, the server requires the `version` in `package.json` to be **strictly higher** (per [semver](https://semver.org) ordering) than the currently deployed version. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
So veröffentlichen Sie ein Update:
-1. Erhöhen Sie das Feld `version` in Ihrer `package.json`
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. Führen Sie `yarn twenty deploy` aus (oder `yarn twenty deploy --remote production`)
3. Arbeitsbereiche, die die App installiert haben, sehen in ihren Einstellungen, dass ein Upgrade verfügbar ist.
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## Auf npm veröffentlichen
@@ -189,3 +195,12 @@ Sie können Apps auch über die Befehlszeile installieren:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>
diff --git a/packages/twenty-docs/l/it/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/it/developers/extend/apps/publishing.mdx
index 8c44c23932d..1b85c2aa185 100644
--- a/packages/twenty-docs/l/it/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/it/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ Il link di condivisione utilizza l'URL di base del server (senza alcun sottodomi
### Gestione delle versioni
+When updating an already deployed tarball app, the server requires the `version` in `package.json` to be **strictly higher** (per [semver](https://semver.org) ordering) than the currently deployed version. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
Per rilasciare un aggiornamento:
-1. Incrementa il campo `version` nel tuo `package.json`
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. Esegui `yarn twenty deploy` (oppure `yarn twenty deploy --remote production`)
3. Gli spazi di lavoro che hanno l'app installata vedranno l'aggiornamento disponibile nelle proprie impostazioni
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## Pubblicazione su npm
@@ -189,3 +195,12 @@ Puoi anche installare le app dalla riga di comando:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>
diff --git a/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx
index 12c435b0cae..6074f23c6a9 100644
--- a/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/pt/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ O link de compartilhamento usa a URL base do servidor (sem qualquer subdomínio
### Gerenciamento de versões
+When updating an already deployed tarball app, the server requires the `version` in `package.json` to be **strictly higher** (per [semver](https://semver.org) ordering) than the currently deployed version. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
Para lançar uma atualização:
-1. Atualize o campo `version` no seu `package.json`
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. Execute `yarn twenty deploy` (ou `yarn twenty deploy --remote production`)
3. Os espaços de trabalho que têm o aplicativo instalado verão a atualização disponível em suas configurações
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## Publicação no npm
@@ -189,3 +195,12 @@ Você também pode instalar apps pela linha de comando:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>
diff --git a/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx
index 788f5e86aff..c12aad09876 100644
--- a/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ yarn twenty deploy
### Управление версиями
+When updating an already deployed tarball app, the server requires the `version` in `package.json` to be **strictly higher** (per [semver](https://semver.org) ordering) than the currently deployed version. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
Чтобы выпустить обновление:
-1. Обновите значение поля `version` в файле `package.json`
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. Выполните `yarn twenty deploy` (или `yarn twenty deploy --remote production`)
3. Рабочие пространства, в которых установлено приложение, увидят доступное обновление в своих настройках
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## Публикация в npm
@@ -189,3 +195,12 @@ jobs:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>
diff --git a/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx
index 6c0fb442e21..688aea8c1f7 100644
--- a/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx
+++ b/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx
@@ -66,12 +66,18 @@ Paylaşım bağlantısı, sunucunun temel URL’sini (herhangi bir çalışma al
### Sürüm yönetimi
+When updating an already deployed tarball app, the server requires the `version` in `package.json` to be **strictly higher** (per [semver](https://semver.org) ordering) than the currently deployed version. Re-deploying the same version, or pushing a lower one, is rejected before the tarball is stored — you'll see a `VERSION_ALREADY_EXISTS` error from the CLI.
+
Bir güncelleme yayımlamak için:
-1. `package.json` içindeki `version` alanını artırın
+1. Bump the `version` field in your `package.json` (e.g. `1.2.3` → `1.2.4`, `1.3.0`, or `2.0.0`)
2. `yarn twenty deploy` (veya `yarn twenty deploy --remote production`) komutunu çalıştırın
3. Uygulamayı kurmuş olan çalışma alanları, ayarlarında mevcut güncellemeyi görecektir
+<Note>
+Pre-release tags work as expected: bumping `1.0.0-rc.1` → `1.0.0-rc.2` is allowed, and a final release like `1.0.0` is correctly recognized as higher than `1.0.0-rc.5`. The version in `package.json` must itself be a valid semver string.
+</Note>
+
{/* TODO: add screenshot of the Upgrade button */}
## npm’ye yayımlama
@@ -189,3 +195,12 @@ Uygulamaları komut satırından da yükleyebilirsiniz:
```bash filename="Terminal"
yarn twenty install
```
+
+<Note>
+The server enforces semver versioning on install, mirroring the rules on deploy:
+
+* Installing the same version that is already installed in your workspace is rejected with an `APP_ALREADY_INSTALLED` error.
+* Installing a lower version than the one currently installed is rejected with a `CANNOT_DOWNGRADE_APPLICATION` error.
+
+To install a newer version, deploy or publish it first, then re-run `yarn twenty install`.
+</Note>