Version 3.2.0

Add file_ext optional parameter to further customize file searching process:

• file_ext — Custom file extension to use when searching for translation files (without leading dot). By default, the extension is inferred from the file_format value. However, for certain formats (e.g., json_structured), the downloaded files may still have a generic extension (e.g., .json). In such cases, this parameter allows specifying the correct extension manually to ensure proper file matching. This parameter has no effect when the name_pattern is provided.

Version 3.1.2

Make tags fetching more robust to avoid re-creation of an already existing tag

Version 3.1.1

Handle more complex cases with custom naming pattern

Version 3.1.0

Added new input params:

• name_pattern — Custom pattern for naming translation files. Overrides default language-based naming. Must include both filename and extension if applicable (e.g., "custom_name.json" or "**.yaml"). Default behavior is used if not set.
  • When the name_pattern is set, the action will respect your translations_path but won't append any language names as folders. Therefore, if you want to upload all JSON files with custom naming for the English locale, you'll need to provide name_pattern: "en/**/custom_*.json". To upload all JSON files stored directly under translations_path, you'll set name_pattern: "custom_*.json". The latter approach is similar to flat_naming but enables you to define custom patterns.
• skip_tagging — Do not assign tags to the uploaded translation keys on Lokalise. Set this to true to skip adding tags like inserted, skipped, or updated keys. Defaults to false.
• rambo_mode — Always upload all translation files for the base language regardless of changes. Set this to true to bypass change detection and force a full upload of all base language translation files. Defaults to false.

Added new output params:

• initial_run — Indicates whether this is the first run on the branch. The value is true if the lokalise-upload-complete tag does not exist, otherwise false.
• files_uploaded — Indicates whether any files were uploaded to Lokalise. The value is true if files were successfully uploaded, otherwise false (e.g., no changes or upload step skipped).

Version 3.0.0

• Full rewrite of the major steps in Go. Use precompiled binaries
• Add flat_naming param to handle cases when translation files are stored right under translations_path. Learn more: https://developers.lokalise.com/docs/github-actions#translation-files
• Add new optional parameters to control timeouts, check https://github.com/lokalise/lokalise-push-action?tab=readme-ov-file#optional-parameters

Version 2.0.0

• Breaking change: translations_path now accepts a list of paths, for example:

      - name: Push to Lokalise
        uses: lokalise/[email protected]
        with:
          api_token: ${{ secrets.LOKALISE_API_TOKEN }}
          project_id: LOKALISE_PROJECT_ID
          base_lang: BASE_LANG_ISO
          translations_path: |
            TRANSLATIONS_PATH1
            TRANSLATIONS_PATH2
          file_format: FILE_FORMAT
          additional_params: ADDITIONAL_CLI_PARAMS

• Various code tweaks

Version 1.0.0

The first stable version published to GitHub Marketplace

Version 0.1.0

Initial release