v2

What's new in v2

Exclude files from formatting

Add an optional .palantir-java-format-exclude file at the repository root. Every non-empty,
non-comment line is a git pathspec (relative to the repo root); any matching Java file is skipped.
It is the single source of exclusions, honoured by both the action and the pre-commit hook —
see Excluding files.

# .palantir-java-format-exclude
samples/**
**/build/generated/**

More robust version check

The "a newer formatter is available" check no longer fails the build. It now authenticates with the
job token to avoid GitHub API rate-limit (403) errors, and degrades to a friendly skip message on
any failure instead of aborting the job.

Other

• Default version bumped to 2.96.0.

Usage

- uses: actions/checkout@v4

- uses: abashev/palantir-java-format-action@v2
  with:
    version: '2.96.0'

Full changelog: v1...v2

v1

v1.0.0

GitHub Action for checking Java code formatting with palantir-java-format.

Features

• Native binary — uses GraalVM native image from Maven Central, no Java/Maven/Gradle required
• Smart file detection — in mode: changed automatically picks up files from PR or push commits
• Binary caching — caches the formatter binary via actions/cache to speed up subsequent runs
• Configurable version — supports any published version of palantir-java-format-native

Inputs

Input	Default	Description
version	2.89.0	Version of palantir-java-format
mode	changed	changed — files from PR/push; all — every .java file

Quick start

- uses: actions/checkout@v4

- uses: abashev/palantir-java-format-action@v1
  with:
    version: '2.89.0'

Supported platforms

• Linux x86_64
• Linux aarch64
• macOS aarch64 (Apple Silicon)