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.

Generally, to fix this problem you add a permissions: block either at the top level of the workflow (to apply to all jobs) or within specific jobs, explicitly declaring the least privileges your workflow needs. For a build job that only needs to read the repository contents and possibly packages, a minimal safe default is contents: read. You can expand scopes later if the workflow requires it.

For this specific file, .github/workflows/build.yml, the simplest non-breaking fix is to add a root-level permissions section that applies to the build job which reuses the external workflow. This keeps behavior as close as possible to current behavior while constraining GITHUB_TOKEN to read-only repository contents by default. Concretely, insert:

permissions:
  contents: read

between the on: block and the jobs: block. No imports or additional methods are needed; this is purely a YAML configuration change.