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 terms, the fix is to explicitly define a permissions section for the workflow (globally) or for the build job so that the GITHUB_TOKEN is limited to the minimum necessary scopes, instead of inheriting potentially broad repository defaults. For a typical Maven build that only needs to fetch source and dependencies, contents: read is an appropriate minimal starting point.

The best targeted fix without changing existing functionality is to add a permissions block to the build job in .github/workflows/build.yml. Since this job simply calls a reusable workflow, and we have no evidence it requires write access, we will set contents: read at the job level. This ensures that, regardless of org/repo defaults, the token available to this job and passed to the reusable workflow remains read-only for repository contents. Concretely, in .github/workflows/build.yml, under jobs:, within the build: job and at the same indentation level as uses:, insert:

    permissions:
      contents: read

No additional methods, imports, or definitions are needed; this is purely a YAML configuration change inside the existing workflow file.