Version 3.5.0

Add new optional params:

• git_user_name — Optional Git username to use when tagging the initial Lokalise upload. If not provided, the action will default to the GitHub actor that triggered the workflow. This is useful if you'd like to show a more descriptive or bot-specific name in your Git history (e.g., "Lokalise Sync Bot").
• git_user_email — Optional Git email to associate with the Git tag for the initial Lokalise upload. If not set, the action will use a noreply address based on the username (e.g., username@users.noreply.github.com). Useful for customizing commit/tag authorship or when working in teams with dedicated automation accounts.

Version 3.4.2

• Lock dependency actions to commits
• Lock Lokalise CLIv2 to 3.1.1

Version 3.4.1

• Use install-lokalise-cli-v2 from Lokalise org account

Version 3.4.0

• Update additional params handling:

additional_params: |
  --convert-placeholders
  --hidden-from-contributors

• Lock bodrovis/install-lokalise-cli-v2 to v1.1.0

Version 3.3.0

Added new option parameters:

• os_platform — Target platform for the precompiled binaries used by this action (linux_amd64, linux_arm64, mac_amd64, mac_arm64). Default is linux_amd64
• skip_polling — Skips waiting for the upload operation to complete. When set to true, the upload_poll_timeout parameter is ignored. Defaults to false.
• skip_default_flags — Prevents the action from setting additional default flags for the upload command. By default, the action includes --replace-modified --include-path --distinguish-by-file. When skip_default_flags is true, these flags are not added. Defaults to false.

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