v6.3.0

Behavior change: Java problem matcher is now opt-in

Starting with v6.3.0, setup-java no longer registers the Java problem matcher by default (#1326, fixes #1322). Java compiler warnings, compiler errors, and uncaught exceptions are no longer turned into annotations on pull request diffs unless you opt in.

To keep annotations, set problem-matcher: true:

- uses: actions/setup-java@v6
  with:
    distribution: temurin
    java-version: '25'
    problem-matcher: true

Compiler output still appears in the build logs, and compilation errors still fail the build. Only annotations are affected.

Why: inline annotations cluttered pull request reviews, and GitHub Actions caps annotations at 10 errors, 10 warnings, and 10 notices per step, and 50 per job. Larger Java builds therefore showed only a truncated subset of their diagnostics as annotations. See Java problem matcher (compiler annotations).

What's Changed

• Architecture validation for JDK file installs by @v-mahabaleshwars in #1324
• chore(deps): bump fast-xml-parser from 5.11.2 to 5.12.0 by @dependabot[bot] in #1323
• Add Microsoft OpenJDK 25.0.5.0.2 support by @brunoborges with @Copilot in #1320
• Fix JetBrains Runtime hotfix version selection by @brunoborges with @Copilot in #1321
• Make Java problem matcher opt-in (default problem-matcher to false) by @brunoborges in #1326

Full Changelog: v6.2.0...v6.3.0