lokalise-deploy-integration

# Lokalise Deploy Integration ## Overview Translations must be downloaded fresh during CI/CD builds to ensure production always ships the latest reviewed content. This skill covers downloading translations as a build step, GitHub Actions workflows for translation sync, Vercel and Netlify build plugin integration, OTA (over-the-air) updates for mobile apps via Lokalise's iOS and Android SDKs, and environment-specific translation bundles. ## Prerequisites - Lokalise API token with download permissions (read-only token recommended for CI) - `LOKALISE_API_TOKEN` and `LOKALISE_PROJECT_ID` stored as CI secrets - `curl` and `unzip` available in CI environment (standard on GitHub Actions runners) - For OTA: Lokalise OTA SDK token (separate from API token, generated in Lokalise dashboard) ## Instructions ### 1. Download Translations in the Build Step Add a pre-build script that pulls translations from Lokalise before your framework compiles: ```bash #!/bin/bash # scripts/download-translations.sh set -euo pipefail PROJECT_ID="${LOKALISE_PROJECT_ID:?Missing LOKALISE_PROJECT_ID}" API_TOKEN="${LOKALISE_API_TOKEN:?Missing LOKALISE_API_TOKEN}" DEST_DIR="${1:-./src/locales}" echo "Downloading translations for project $PROJECT_ID..." BUNDLE_URL=$(curl -sf -X POST \ "https://api.lokalise.com/api2/projects/${PROJECT_ID}/files/download" \ -H "X-Api-Token: ${API_TOKEN}" \ -H "Content-Type: application/json" \ -d "{ \"format\": \"json\", \"original_filenames\": false, ...