Releases: locize/locize-cli
Releases · locize/locize-cli
Release list
v12.5.1
- install: the SheetJS
xlsxdependency is no longer fetched from cdn.sheetjs.com
at install time; the same 0.20.3 build (integrity-verified, Apache-2.0 license
included) is now vendored and compiled into the package. npm 12 blocks remote
tarball dependencies by default (allow-remote=none), which made installing
locize-cli fail; pnpm needed a similar workaround before
(117,
116).
v12.5.0
- sync: removed keys are now listed by name in real runs too (previously the
names were only shown with--dry), capped at 50 keys per namespace, so a
sync always shows exactly what it deleted. When keys are removed without
--backup-deleted-path, a one-line tip now points to-Bto keep a local
backup of the removed segments (98). - remove: accepts multiple keys (
locize remove common title subtitle ...),
batched into a single update request per language (53). - docs: README notes for pnpm >= 11 (
blockExoticSubdepsand whyxlsxis
pinned to the SheetJS CDN tarball) and for the xcstrings format (file-level
conversion; i18next plural suffixes /{{...}}interpolation are not
rewritten to String Catalog plural variations / format specifiers).
v12.3.1
- request: retry transient network failures with exponential backoff and jitter
instead of a fixed 5s delay. This spreads retries so that bursts of
concurrent CLI runs (e.g. in CI) no longer retry in lockstep and hit the API
at the same instant.
v12.3.0
- sync: creates missing remote languages on the fly. A project without any
languages yet is bootstrapped automatically from the local language folders
(or--language/--languages), and a language that exists locally but not
in the project is created too instead of being silently ignored — the server
decides whether the api-key may (admin keys always; any write-capable key
while the project still has no content). On rejection sync warns and
continues;--drynever creates languages. - migrate: also works on a project without any languages yet (previously both
sync and migrate failed with a misleading "Project not found" error when the
project's languages file was empty). - fix: the "wrong cdnType" hint no longer crashes (or fires) when the other
endpoint answers with a non-JSON response; the empty-project error now reads
"Project … not found — or it has no languages yet!" and carries an
EMPTY_LANGUAGES/WRONG_CDN_TYPEerror code for programmatic consumers.