Update GitHub Action Versions

[morisil]

GitHub Actions Version Updates

• actions/setup-java published a new release v5.6.0 on 2026-07-16T14:46:41Z
• anthropics/claude-code-action published a new release v1.0.178 on 2026-07-19T02:57:25Z

[claude]

Review

Overview

Routine, automated dependency bump (via action-version-updater.yml):

• actions/setup-java v5.5.0 → v5.6.0 in build-gradle.yml
• anthropics/claude-code-action v1.0.175 → v1.0.178 in claude-code-review.yml and claude-code.yml

Code quality & conventions

• Diff is minimal and scoped exactly to the version bumps — no unrelated changes.
• Consistent with the repo's existing convention of pinning actions to specific version tags (e.g. actions/checkout@v7.0.0 nearby is unchanged and follows the same pattern).
• Both claude-code.yml and claude-code-review.yml are bumped together, keeping the claude-code-action version consistent across reusable workflows — good, avoids drift between the two.

Potential issues / risks

• Tag pinning vs. SHA pinning: version tags (@v5.6.0, @v1.0.178) are mutable refs, not immutable like commit SHAs. This is pre-existing repo convention, not something introduced by this PR, but worth noting as a general hardening opportunity for supply-chain integrity (pin third-party actions by SHA with a version comment) if the org wants tighter security guarantees down the line.
• No functional/behavioral risk expected — these are patch/minor version bumps of well-maintained, widely-used actions.

Test coverage

• No tests apply to this change (workflow YAML version bumps); nothing to add here. The real "test" is the next CI run exercising build-gradle.yml and the two Claude workflows, which will validate the new versions work as expected.

Verdict

Looks good — low risk, mechanical, and consistent with existing patterns. No changes requested.