Update 8hobbies/workflows digest to 4443153

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
8hobbies/workflows	action	digest	0addb4a -> 4443153

---

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 to .github/workflows/lint.yml either at the root level—so it applies to all jobs in the workflow that do not have their own permissions key—or inside the lint job. Since the only job is lint, and it uses a reusable workflow, you can add the permissions block either right under jobs:, or the root of the workflow (after name, usually). The minimally required permission for a linting workflow is typically contents: read, but if you know it needs additional permissions (like commenting on pull requests), you can add those. Since you only have access to this job, it is safest to add a minimal block: permissions: contents: read.

Edit .github/workflows/lint.yml to add:

permissions:
  contents: read

immediately after the name: block (before on:), or within the lint: job as:

permissions:
  contents: read

The fix does not require any imports, definitions, or further changes.

To fix the problem, you should add an explicit permissions block at the root level of the workflow in .github/workflows/runtime.yml. This block should minimally restrict permissions for the entire workflow unless a job overrides it. Since the job delegates all execution to a reusable workflow using uses:, and unless there are requirements for write access (such as creating releases, updating issues, etc.), the safest baseline is contents: read. This reduces GITHUB_TOKEN access to read-only. If workflow functionality requires elevated or more granular permissions, the block should be adjusted accordingly. To implement, insert the permissions: block after the name: and before the on: section (ideally line 16 or 17).