Update 8hobbies/workflows digest to b4d993f

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Type	Update	Change
8hobbies/workflows	action	digest	05401f5 -> b4d993f

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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.

To fix the problem, you should add a permissions block at the root level of the workflow file (.github/workflows/lint.yml). This ensures the GITHUB_TOKEN receives only the minimum required privileges (typically just contents: read for a lint workflow). This block should be inserted below the workflow name (name: Lint) but above the on: specification so it's clear and applies globally to all jobs unless further restricted. No other code changes or imports are necessary; simply add the following YAML block:

permissions:
  contents: read

This restricts the workflow GITHUB_TOKEN to read repository contents, which is sufficient for a lint workflow and adheres to the principle of least privilege.

To fix the issue, you should add an explicit permissions block to the workflow file. This can be done at the workflow level (top-level, applying to all jobs unless overridden) or at the job level (within jobs.run). Since the job simply invokes a reusable workflow (and the file is otherwise minimal), it is most appropriate and future-proof to add the permissions block at the top level—just after the name or on blocks. The safest minimal set (if the invoked workflow only needs to read the contents) is contents: read; if it needs additional permissions, you can expand as needed. In the absence of specific requirements, contents: read is the recommended starting point.

To resolve the issue, add a permissions block declaring the minimum required GitHub token permissions for the workflow at the top level, or within the job definition. Since there is only one job and it's a directly-used reusable workflow, the best place is at the root level (global for the workflow) after the name: and before on:. If you don't know the minimum permissions needed, you should start with the minimal recommended (e.g. contents: read) and refine later if workflows actually require more. No other changes are needed.