fix(workflows/lock): bump dessant/lock-threads v6.0.0 → v6.0.2#145
Merged
Conversation
GitHub recently changed the GITHUB_TOKEN format to a longer string. dessant/lock-threads v6.0.0 has a hardcoded validation that rejects tokens longer than 100 characters: ##[error]"github-token" length must be less than or equal to 100 characters long This breaks every consumer of `netresearch/.github/.github/workflows/lock.yml@main` on every scheduled cron run (00:00 UTC daily across ~30 NR repos). Three failures observed so far: t3x-nr-textdb #91, t3x-nr-temporal-cache #91, t3x-nr-image-optimize #146. v6.0.2 (released 2026-05-23) explicitly fixes this: ### Bug Fixes * update github-token validation schema (closes #55) https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#602-2026-05-23 dessant/lock-threads#55 Pin: dessant/lock-threads@89ae32b # v6.0.2 (commit SHA the v6.0.2 tag points to — verified via gh api). Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
There was a problem hiding this comment.
Pull request overview
This PR updates the reusable GitHub Actions workflow .github/workflows/lock.yml to use dessant/lock-threads v6.0.2 (pinned by commit SHA), addressing a regression where v6.0.0 rejects newer, longer GITHUB_TOKEN values and breaks scheduled runs for downstream repositories.
Changes:
- Bump
dessant/lock-threadsfrom v6.0.0 to v6.0.2 (commit-SHA pinned) inlock.yml.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Summary
Bumps
dessant/lock-threadsfromv6.0.0tov6.0.2in.github/workflows/lock.ymlto fix a GITHUB_TOKEN validation regression that is breaking the dailyCommunityworkflow run across every NR repo that consumeslock.yml@main.Root cause
GitHub recently changed the
GITHUB_TOKENformat to a longer string.dessant/lock-threads@v6.0.0(currently pinned) has a hardcoded schema validation that rejects tokens longer than 100 characters:This breaks every consumer of
netresearch/.github/.github/workflows/lock.yml@mainon every scheduled cron run (00:00 UTC daily). Observed today (2026-05-23) on at least:netresearch/t3x-nr-textdbCommunity #91netresearch/t3x-nr-temporal-cacheCommunity #91netresearch/t3x-nr-image-optimizeCommunity #146The full blast radius is every NR repo whose Community workflow calls
lock.yml@main— ~30 repos.Why v6.0.2 is the fix
From the upstream CHANGELOG entry for v6.0.2:
Released today (2026-05-23) specifically to address this. v6.0.1 (released 2026-05-21) only updated dependencies and doesn't fix the schema.
Pin
dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2— commit SHA thev6.0.2tag points to, resolved viagh api repos/dessant/lock-threads/git/refs/tags/v6.0.2. Renovate will keep this current via the standard# vX.Y.Zcomment pattern.Verification
actionlint .github/workflows/lock.yml→ cleanyamllintagainst CI defaults → cleanAfter merge, the daily 00:00 UTC Community runs across consuming repos should self-correct on the next scheduled trigger.