From dc5335f3eca79a5840a6a31548c103cf01a60a70 Mon Sep 17 00:00:00 2001 From: SatoshiQaziMuhammed Date: Fri, 13 Nov 2026 18:45:05 +0400 Subject: [PATCH] ci: move Lock Threads to dessant/lock-threads v6.0.2 (#23) The pinned v4.0.0 rejects the job token: it validates github-token at 100 characters or fewer, and Actions tokens are now longer, so every scheduled run fails with '"github-token" length must be less than or equal to 100 characters long'. v6.0.2 accepts them. Permissions follow the workflow phishing already runs: empty top-level permissions, issues/pull-requests write on the job only, process-only issues and PRs (discussions write is no longer granted), and a 10 minute timeout. Each repository keeps its schedule. --- .github/workflows/lock.yml | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index 8df7b46..97b767a 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -5,17 +5,20 @@ on: - cron: '0 0 * * *' workflow_dispatch: -permissions: - issues: write - pull-requests: write +permissions: {} jobs: lock: runs-on: ubuntu-latest + timeout-minutes: 10 + permissions: + issues: write + pull-requests: write steps: - - uses: dessant/lock-threads@v5 + - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2 with: github-token: ${{ github.token }} + process-only: 'issues, prs' issue-inactive-days: 30 pr-inactive-days: 30 issue-lock-reason: resolved