From b7f6981d256fa6438723ea97c1eab1ca07e6fe87 Mon Sep 17 00:00:00 2001 From: Tushar Pagar Date: Tue, 13 Oct 2026 13:46:38 +0530 Subject: [PATCH] ci: bump lock-threads to v6 so the scheduled lock job can run (#13693) The pinned version validates its github-token input with a 100 character cap, and the Actions token now exceeds that, so every run fails before locking anything: ##[error]"github-token" length must be less than or equal to 100 characters long v6 raised the cap to 1000 (v4 and v5.0.x both still validate max(100)). Every input this workflow passes exists unchanged in the v6 schema, so the pin bump is the whole fix. Pinned to the v6.0.2 release commit. Co-authored-by: Tushar Pagar <240662211+tushardev-365@users.noreply.github.com> --- .github/workflows/lock.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index 7cbfe6c6c..fe254aa01 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -15,7 +15,7 @@ jobs: pull-requests: write # for dessant/lock-threads to lock PRs runs-on: ubuntu-latest steps: - - uses: dessant/lock-threads@1bf7ec25051fe7c00bdd17e6a7cf3d7bfb7dc771 # v5.0.1 + - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2 with: github-token: ${{ github.token }} issue-comment: >