From 3866d6fd2b593cf85c041e13f258db1c2148f5a5 Mon Sep 17 00:00:00 2001 From: "Sebastian \"Sebbie\" Silbermann" Date: Tue, 1 Sep 2026 17:50:10 +0200 Subject: [PATCH 1/2] [ci] Fix `issue_lock` (#97755) Fixes > "github-token" length must be less than or equal to 100 characters long -- https://github.com/vercel/next.js/actions/runs/33188474239 GitHub uses stateless tokens now which are way longer. See https://github.com/dessant/lock-threads/issues/55 --------- Co-authored-by: Claude Code (kimi-k3[1m]) --- .github/workflows/issue_lock.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/issue_lock.yml b/.github/workflows/issue_lock.yml index b58487c7fdb1..6e8af2f1548d 100644 --- a/.github/workflows/issue_lock.yml +++ b/.github/workflows/issue_lock.yml @@ -18,7 +18,7 @@ jobs: runs-on: ubuntu-latest if: github.repository_owner == 'vercel' steps: - - uses: dessant/lock-threads@1bf7ec25051fe7c00bdd17e6a7cf3d7bfb7dc771 # v5.0.1 + - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2 with: github-token: ${{ secrets.GITHUB_TOKEN }} add-issue-labels: 'locked' From 52cd5b96ab440279075f189ddc34e31249684be6 Mon Sep 17 00:00:00 2001 From: "Sebastian \"Sebbie\" Silbermann" Date: Tue, 1 Sep 2026 20:06:18 +0200 Subject: [PATCH 2/2] Skip discussions in the `issue_lock` workflow (#98146) The last remaining `Lock Threads` failures are likely due to missing permissions for discussions which `dessant/lock-threads` handles by default. This disables discussion handling to get the workflow green to start tracking regressions. We can discuss if we want to lock inactive discussions in a follow-up (which would be new behavior this workflow never performed). Co-authored-by: Claude Code (kimi-k3[1m]) --- .github/workflows/issue_lock.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/issue_lock.yml b/.github/workflows/issue_lock.yml index 6e8af2f1548d..6e4cb599bf22 100644 --- a/.github/workflows/issue_lock.yml +++ b/.github/workflows/issue_lock.yml @@ -27,3 +27,6 @@ jobs: issue-comment: 'This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.' pr-inactive-days: 14 log-output: true + # The token has no `discussions` permission and discussions are not + # meant to be locked, so skip them (they are processed by default). + process-only: 'issues, prs'