Releases: Smartling/smartling-cli
3.4
Smartling CLI 3.4
New: glossaries command group
Manage Smartling glossaries directly from the CLI - create them, and move terms in and out in CSV, XLSX, or TBX formats.
smartling-cli glossaries create <name>- create a glossary with one or more locales, an optional description, and fallback-locale mappings (--locale,--description,--fallback-locale).smartling-cli glossaries list- list/search glossaries in the account, filterable by name (--name); supportssimple,table, andjsonoutput.smartling-cli glossaries export <uid|name> [outFile]- export glossary entries to CSV / XLSX / TBX, with locale selection (--locale), TBX version (--tbx-version), and rich--filter-*options (query, entry state, labels, created/modified date & user, and more). IfoutFileis omitted it writes to<glossaryUID>.<file-type>.smartling-cli glossaries import <uid|name> <inFile>- upload a CSV / XLSX / TBX file into an existing glossary, with--archive-modeand--media-typeoverride; the import is confirmed and polled to completion, reporting entry changes and warnings.
All four commands accept a glossary by UID or name, honor smartling.yml configuration (including --account fallback), and support the global --output format flag.
3.3.1
Smartling CLI 3.3.1
Bug fix - files push, files pull, and other file commands failed with parameter AccountUID cannot be empty for users whose smartling.yml does not include account_id. No config changes required to upgrade.
3.3
Smartling CLI 3.3
Migrated to GoReleaser for cross-platform builds.
3.2
Smartling CLI 3.2
New Features
jobs progresscommand - track translation progress for a job (CON-1896, #95)- Bulk download of files attached to a job (RPS-10045, #101)
- Account and project information banner shown at startup with
--show-config(RPS-10094, #103)
Technical
- Smaller release binaries via build flags (#102)
3.0
Smartling CLI 3.0
New Features
upload/downloadaliases forpush/pullcommands (#88)--nojoboption for theuploadcommand to skip job creation (CON-1842, #91)--alloption for thedownloadcommand to fetch all files (CON-1843, #93)- Job information returned after upload (CON-1837, #89)
Improvements
- Updated output format for
mt translate(CON-1844, #90) - Parameter validation for commands (CON-1846, #92)
- Informative log message when no file is downloaded (CON-1870, #94)
- Updated documentation for file commands
Technical
2.5
2.4.1
2.4
2.3
Bug Fixes
- Fixed the
files pushcommand to support file upload directives.
2.2
New Features
Job-based File Uploads: The files push command now uploads all files as part of a Smartling Job by default. This provides better organization and workflow management for translation projects.
Learn more about Smartling Jobs:
Breaking Changes
The files push command includes one new flag and two updated flags:
New Flag
-j,--job <job name>- Specifies the Smartling translation job name or job UID. All files upload to this job. If not specified, defaults to "CLI uploads".
Updated Flags
-z,--authorize- Automatically authorizes the job with uploaded files and specified locales. Without this flag, the job remains unauthorized.-l,--locale <locale code>- Adds files to the job for the specified locale only. Without this flag, files are added for all project locales. Can be used multiple times:--locale fr --locale de -l es.
Recommended Usage
smartling-cli files push <file> <uri> --job <job name> [--authorize] [--locale <locale>] [flags]Backward Compatibility
CLI v2.2 maintains compatibility with the previous files push format. However, we recommend updating to the new format.
Legacy Command Behavior
smartling-cli files push <file> <uri>When using the legacy format (without job name and locale):
- Creates or reuses a job named "CLI uploads"
- Attaches the file to all project locales
- Leaves the job unauthorized
Migration Guide
-
Add the
--jobflag to existing commands and specify a job name or UID- The same job name can be used across multiple CLI calls
- CLI searches by job name and reuses existing jobs
- If a job with the same name exists in
CanceledorClosedstate, a new job is created with a timestamp suffix
-
Review locale targeting by explicitly adding the
--localeflag if you need specific locales- Without
--locale, CLI targets all project locales
- Without
-
Consider authorization by adding the
--authorizeflag if you want automatic content authorization- Without
--authorize, jobs remain unauthorized and require manual authorization
- Without