lingo.dev@0.136.2

Patch Changes

• Updated dependencies [7893f5b]:
  • @lingo.dev/_sdk@0.16.4
  • @lingo.dev/_compiler@0.12.4

lingo.dev@0.136.1

Patch Changes

• #2096 7d803d2 Thanks @louisguitton! - Install git in the lingodotdev/ci-action Docker image so lingo.dev ci works in runners that do not already provide it (e.g. GitLab CI using the image directly).

• #2095 fd11342 Thanks @Waqasabid99! - Fix parsing of comma-separated locale inputs with spaces and quotes during init

@lingo.dev/_sdk@0.16.4

Patch Changes

• #2103 7893f5b Thanks @AndreyHirsa! - Android-format (pt-rPT) and underscore (pt_PT) locales passed config validation but were sent to the API verbatim, which it rejects with a 400. Normalize sourceLocale, targetLocale, and reference keys to canonical BCP 47 on the wire via a schema transform. File paths are unaffected, so the CLI keeps the original code for Android resource directories (e.g. values-pt-rPT/)

@lingo.dev/_compiler@0.12.4

Patch Changes

• Updated dependencies [7893f5b]:
  • @lingo.dev/_sdk@0.16.4

lingo.dev@0.136.0

Minor Changes

• #2093 74c8be0 Thanks @cherkanovart! - Change the default behavior of lingo.dev lockfile so it fills in missing i18n.lock sections additively instead of bailing out. Without --force, sections that already contain checksums are left untouched (preserving the divergence signal that --frozen relies on), and any pathPattern whose section is missing or empty is populated from the current source. --force still rebuilds the entire lock as before.

  Update the --frozen validation error to point users at the recovery command: messages now read "Run lingo.dev lockfile to refresh i18n.lock, or run without --frozen."

  Together these surface a fix for the false-positive --frozen failures that PR #2091 did not cover (new files under ** globs, new buckets, prior --target-locale runs that don't write checksums, and pre-existing empty lock sections).

@lingo.dev/compiler@0.4.3

Patch Changes

• Updated dependencies [74c8be0]:
  • lingo.dev@0.136.0

lingo.dev@0.135.1

Patch Changes

• #2091 bf06078 Thanks @cherkanovart! - Fix --frozen falsely reporting "Source file has been updated" after a no-op run. When lingo.dev run finds nothing to translate (source matches target), it now persists source checksums to i18n.lock so a subsequent --frozen run has a baseline to validate against.

lingo.dev@0.135.0

Minor Changes

• #2089 0106b48 Thanks @cherkanovart! - Support recursive glob patterns (**) in bucket include/exclude.

  Patterns like config/locales/**/[locale].yml or src/**/[locale]/strings/*.json now match files at any depth, so you no longer need to enumerate every nesting level. The previous restriction that rejected any pattern containing ** has been removed.

  Two safety nets ship with this change, both scoped to patterns that actually use **:

  • For ** patterns only, node_modules, .git, dist, build, .next, and .turbo are excluded by default so a broad pattern like **/[locale].json does not descend into vendored or build trees. Existing patterns without ** keep the previous traversal behavior exactly as before. Add your own exclude entries on top as needed.
  • When a matched file cannot be unambiguously mapped back to the [locale] placeholder (for example, a pattern with multiple wildcards around [locale] that admits more than one valid restoration), the CLI now throws a clear error instead of silently returning a malformed path.

@lingo.dev/compiler@0.4.2

Patch Changes

• Updated dependencies [0106b48]:
  • lingo.dev@0.135.0

lingo.dev@0.134.0

Minor Changes

• #2087 2787e33 Thanks @moygospadin! - Fix lingo.dev login on Safari (and other browsers that block mixed-content requests to localhost).

  The login command now uses a polling-based device flow: the CLI registers a session with the API, opens the browser to confirm it, then polls until the user grants access. The previous flow opened a local Express server and asked the web page to POST the API key to http://localhost:<port>, which Safari blocks because the page is served over HTTPS. The web app continues to support the legacy ?port= query parameter for one release cycle so CLI versions published before this change keep working in Chrome — Safari users need this upgrade either way. The express and cors dependencies are no longer needed and have been removed.