Repository navigation
Comparing changes
Open a pull request
base repository: openjavaformat/open-java-format-action
base: v2
head repository: openjavaformat/open-java-format-action
compare: main
- 13 commits
- 7 files changed
- 2 contributors
Commits on Sep 23, 2026
-
Check with open-java-format 2.98.0.3
The action, the pre-commit hook and the CI default to 2.98.0.3, released on 2026-09-23. It has the same single style as 2.98.0.2, so this stays on v2.
Configuration menu - View commit details
-
Copy full SHA for 0baea89 - Browse repository at this point
Copy the full SHA 0baea89View commit details
Commits on Sep 25, 2026
-
Check with open-java-format 2.98.0.4
The action, the pre-commit hook and the CI default to 2.98.0.4, released on 2026-09-25. It keeps the single style of 2.98.0.2, so this stays on v2.
Configuration menu - View commit details
-
Copy full SHA for 83d0df8 - Browse repository at this point
Copy the full SHA 83d0df8View commit details
Commits on Sep 28, 2026
-
Check with open-java-format 2.98.0.5
The action, the pre-commit hook and the CI default to 2.98.0.5, released on 2026-09-28. It keeps the single style of 2.98.0.2, so this stays on v2. 2.98.0.5 leaves JBang directives such as //DEPS at the top of a script as written (openjavaformat/open-java-format#24), so the exclude example in the README no longer gives JBang scripts as the reason to skip files. It shows code copied from another project instead.
Configuration menu - View commit details
-
Copy full SHA for 80a52bb - Browse repository at this point
Copy the full SHA 80a52bbView commit details
Commits on Oct 4, 2026
-
Follow open-java-format releases from CI
Until now every open-java-format release meant editing the version by hand in the action, the pre-commit hook, the CI and the README, and pushing the result. The "Follow open-java-format releases" workflow now does that once an hour: .open-java-format-version holds the version the files are on, and when the latest GitHub release differs, the workflow replaces the version everywhere it is named, pushes the bump to main and runs Test Action on it. Test Action gains workflow_dispatch for that run, because a push made with the workflow's own token starts no push-triggered workflow.
Configuration menu - View commit details
-
Copy full SHA for 6e1a02b - Browse repository at this point
Copy the full SHA 6e1a02bView commit details -
Test the action's default version, not a copy of it
The Follow open-java-format releases workflow pushes with its own token, and GitHub refuses such a push when it changes a workflow file: its first run failed with "refusing to allow a GitHub App to create or update workflow .github/workflows/ci.yml without workflows permission". So Test Action no longer passes a version. Its steps run the action with the default from action.yml, which is the version that gets bumped, so that is what the tests should exercise anyway.
Configuration menu - View commit details
-
Copy full SHA for e01fcae - Browse repository at this point
Copy the full SHA e01fcaeView commit details -
Check with open-java-format 2.98.0.6
The action and the pre-commit hook default to 2.98.0.6, which openjavaformat/open-java-format released on 2026-10-04. Made by the "Follow open-java-format releases" workflow: https://github.com/openjavaformat/open-java-format-action/actions/runs/37218368214
Configuration menu - View commit details
-
Copy full SHA for b86c00b - Browse repository at this point
Copy the full SHA b86c00bView commit details
Commits on Oct 17, 2026
-
Report the version check to code scanning
The action warns when a newer open-java-format release is out than the version it runs, but a log warning is easy to miss. The check is now also uploaded to code scanning as a SARIF file: one alert while the version is behind, none once it is current, which closes the alert. It shows under Security → Code scanning and in the "Code scanning results" check of a pull request, placed on the line of the workflow that names the version, so it points at what to change. Alerts are told apart by a fingerprint of that line's text, so they survive the line moving. The upload goes straight to the REST API rather than through github/codeql-action/upload-sarif, which fails the job when the security-events: write permission is missing. This way the upload is best-effort like the check itself: without the permission, without GitHub Code Security on a private repository, or with the read-only token of a fork's pull request, it is skipped with a line in the log and the log warning stays. The new code-scanning input turns it off. Test Action grants the permission to the mode=changed job, so that run exercises the upload, and withholds it from the platform matrix, whose ten runs of the action would all report the same category and must do without the upload anyway.
Configuration menu - View commit details
-
Copy full SHA for 00ed0e4 - Browse repository at this point
Copy the full SHA 00ed0e4View commit details -
Leave the code scanning report off by default
The report needs the security-events: write permission, which the default token does not have, so with it on by default every workflow that uses the action would have to add a permissions block, and one that did not would skip the upload on every run. The code-scanning input now defaults to false; a workflow that wants the alert sets it to true and grants the permission, as the README shows. The example workflow loses the permissions block it no longer needs. Test Action turns the report on in both jobs: with the permission in the mode=changed job, where the upload has to go through, and without it on the first run of the platform matrix, where it has to be skipped without failing the check.
Configuration menu - View commit details
-
Copy full SHA for 29c2b7d - Browse repository at this point
Copy the full SHA 29c2b7dView commit details -
Show a recommended setup with and without code scanning
The README had one recommended setup and, further down, a bare job with the permission for the code scanning report. Now the recommended setup comes in two complete workflows side by side: one that announces a newer open-java-format release in the job log alone, and one that also raises the code scanning alert, with the permissions that takes. The code scanning section points at the second instead of repeating it.
Configuration menu - View commit details
-
Copy full SHA for 63406a5 - Browse repository at this point
Copy the full SHA 63406a5View commit details
Commits on Oct 18, 2026
-
Point the README and the example at v3
v3 is v2 plus the optional code scanning report, so the README and the example workflow now use @V3, and the README says what tells the two apart. The v3 tag is made on this commit.
Configuration menu - View commit details
-
Copy full SHA for 25979c3 - Browse repository at this point
Copy the full SHA 25979c3View commit details
Commits on Oct 19, 2026
-
Take the version from .open-java-format-version
The action took the version as an input and the pre-commit hook pinned its own in FORMATTER_VERSION, so a repository had two places to keep in step, and either could fall behind on its own. Now both read .open-java-format-version from the repository root, and the version input is gone. Without the file, or with something in it that is not a version number, the action and the hook stop and say what to put there. The check for a newer release stays: the log warning and the code scanning alert now point at .open-java-format-version, line 1, which also does away with the search for the line of the workflow that named the version. The hook's help text says to change that one file. This repository already keeps its own version in that file for Follow open-java-format releases, so Test Action runs the action and the hook with it, and now also checks that both refuse to run without it. The version input is gone, so this is v4.
Configuration menu - View commit details
-
Copy full SHA for 47d9951 - Browse repository at this point
Copy the full SHA 47d9951View commit details
Commits on Nov 1, 2026
-
Check with open-java-format 21.0.1
.open-java-format-version names 21.0.1, which openjavaformat/open-java-format released on 2026-11-01, so the tests run the action and the pre-commit hook with it. Made by the "Follow open-java-format releases" workflow: https://github.com/openjavaformat/open-java-format-action/actions/runs/41343240257
Configuration menu - View commit details
-
Copy full SHA for e4033a1 - Browse repository at this point
Copy the full SHA e4033a1View commit details
Commits on Nov 8, 2026
-
Check with open-java-format 21.0.2
.open-java-format-version names 21.0.2, which openjavaformat/open-java-format released on 2026-11-08, so the tests run the action and the pre-commit hook with it. Made by the "Follow open-java-format releases" workflow: https://github.com/openjavaformat/open-java-format-action/actions/runs/42520644475
Configuration menu - View commit details
-
Copy full SHA for d26e2d7 - Browse repository at this point
Copy the full SHA d26e2d7View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2...main