Conversation
This branch has not been deployed
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 35936703327 (2026-09-24), and on each preceding scheduled execution.
The failure comes from inside the action:
The pinned revision (v5-era commit 1bf7ec2) still carries the upstream
github-tokenvalidation schema that caps the input at 100 characters. The automatically-injectedGITHUB_TOKENnow exceeds that length, so the action rejects its default input before locking anything — closed threads have stopped being locked.Upstream fixed the validation schema in v6.0.2 ("update github-token validation schema", closes dessant/lock-threads#55).
Fix
Re-pin the action to the v6.0.2 release commit (
89ae32b0). None of the inputs used in this workflow changed between the pinned revision and v6.0.2, so lock behaviour stays identical once the workflow can run again.