Skip to content

[pull] canary from vercel:canary - #1358

Merged
pull[bot] merged 2 commits into
code:canaryfrom
vercel:canary
Sep 1, 2026
Merged

[pull] canary from vercel:canary#1358
pull[bot] merged 2 commits into
code:canaryfrom
vercel:canary

Conversation

@pull

@pull pull Bot commented Sep 1, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

eps1lon and others added 2 commits September 1, 2026 17:50
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
dessant/lock-threads#55

---------

Co-authored-by: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
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]) <noreply@anthropic.com>
@pull pull Bot locked and limited conversation to collaborators Sep 1, 2026
@pull pull Bot added the ⤵️ pull label Sep 1, 2026
@pull
pull Bot merged commit 52cd5b9 into code:canary Sep 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant