Skip to content

2.2

Choose a tag to compare

View all tags
@dimitrystd dimitrystd released this 21 Jul 15:01
· 18 commits to master since this release
2.2
441a050

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

  1. Add the --job flag 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 Canceled or Closed state, a new job is created with a timestamp suffix

  2. Review locale targeting by explicitly adding the --locale flag if you need specific locales

    • Without --locale, CLI targets all project locales

  3. Consider authorization by adding the --authorize flag if you want automatic content authorization

    • Without --authorize, jobs remain unauthorized and require manual authorization
Assets 5
Loading