Update 8hobbies/workflows digest to 6ffa892

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
8hobbies/workflows	action	digest	23566a1 -> 6ffa892

---

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, add a permissions block at the workflow root level in .github/workflows/lint.yml. This will set explicit, least-privilege permissions for all jobs unless they define overrides. For a lint-only workflow, the minimum required permission is most likely contents: read, since no writing to the repository, issues, or other resources is expected.
The change should be made directly under the workflow name and before the on: block (typically lines 15-16).
No imports or external definitions are required; just add a YAML mapping.

---

To fix this issue, you should add a permissions block at the root of the workflow file, directly under the workflow name: and before the on: block. This restricts the default token permissions for all jobs (including any jobs/external workflows run via uses:). For most publish "dry-run" workflows, contents: read will suffice unless the workflow, or the reusable workflow it calls, explicitly needs additional permissions (such as for creating pull requests or writing packages). Since we don't have details on additional permissions required, the safest minimal starting point per the recommendation is:

permissions:
  contents: read

If in the future the reusable workflow requires additional permissions, you can add them as needed.

Where to edit:
In .github/workflows/publish-dry-run.yml, add the above block after the name: field (line 15 or 16), just before the on: block.

---

To fix this problem without changing the workflow's existing logic or functionality, add a permissions block near the top of the workflow file, immediately after the name: field and before the on: field. This block should specify the least privilege necessary. If you are unsure what is required, the absolute lowest privilege would be contents: read, which permits actions like checking out code but not writing back. If the reusable workflow needs more than read access to repository contents, you would adjust accordingly, but it's always safest to start restrictive.

Steps:

• Add a permissions: block at the workflow root (after name:).
• For minimal privilege, use permissions: contents: read.

---