Conversation
|
金豆 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The scheduled Lock Threads workflow fails on every run — most recently run 35478525947 (2026-09-20) and each preceding execution.
v5 of the action validates the
github-tokeninput with a 100-character cap, but the automatically-injectedGITHUB_TOKENnow exceeds that length, so the action rejects its default input and closed threads are no longer being locked.Upstream fixed the validation schema in v6.0.2 ("update github-token validation schema", closes dessant/lock-threads#55).
Fix
Bump
dessant/lock-threadsv5 → v6. The inputs used in this workflow are unchanged in v6, so lock behaviour stays the same once the workflow runs again.