Update 8hobbies/workflows digest to e113c9f

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
8hobbies/workflows	action	digest	2914730 -> e113c9f

---

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 this problem, you should set the permissions key at the root level of your workflow file, or (alternatively) at the job level, to explicitly restrict the permissions granted to the Actions' GITHUB_TOKEN. Since this is a lint workflow and should not need write permissions to the repository or other resources, the safest minimum is to set permissions: contents: read, unless your lint job really needs broader access. Add the following to the root of .github/workflows/lint.yml, immediately after the name: Lint line (or before on:). No methods or imports are needed.

To resolve this issue, you should add a permissions block to the workflow to explicitly restrict the GitHub Actions GITHUB_TOKEN to the minimum necessary permissions. As the workflow appears to trigger a dry-run publish—which normally only requires read access—you can safely set permissions: contents: read at the top-level. This restricts the token capabilities for all jobs by default, including delegated (reusable) workflow jobs, unless their own configuration overrides it. Make this change directly after the name block and before on: (i.e., between lines 15 and 17). No new packages, imports, or variable definitions are required.

To fix the issue, add an explicit permissions block at the root level of .github/workflows/runtime.yml. This ensures that unless overridden by a job or a reusable workflow, jobs will execute with restricted permissions on the GITHUB_TOKEN. The minimal starting point should be contents: read, which is sufficient for most builds/tests and aligns with least privilege. If the workflow requires additional permissions (for example, to create issues or comment on PRs), only those permissions should be set to write.

The fix should be inserted after the name key and before on:, as per GitHub workflow formatting conventions.

---