Update valitydev/java-workflow action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
valitydev/java-workflow	action	major	v3 → v4

---

Release Notes

valitydev/java-workflow (valitydev/java-workflow)

v4

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

In general, the fix is to explicitly define a permissions block either at the workflow root (applies to all jobs) or under the specific job. Because this workflow contains a single job build that only calls a reusable workflow, we can safely add a root-level permissions block that restricts the GITHUB_TOKEN to read-only repository contents, which is a safe minimal baseline when we don't see any direct write operations in this snippet.

Best single fix without changing existing functionality: add a root-level permissions section directly under the name: line, before the on: block, specifying least-privilege read access to contents (and optionally packages, but we’ll keep it minimal and only define contents: read as a clear, standard baseline). This does not alter the structure or logic of the existing job; it only constrains the automatic GITHUB_TOKEN that GitHub injects.

Concretely, in .github/workflows/build.yml, insert:

permissions:
  contents: read

after line 1 (name: Maven Build Artifact) and before line 3 (on:). No additional imports or methods are needed since this is a YAML workflow configuration change only.