Skip to content

Bump dessant/lock-threads to v6 to fix token validation error - #1952

Merged
diemol merged 1 commit into
trunkfrom
fix-lock-threads-token
Oct 6, 2026
Merged

diemol merged 1 commit into
trunkfrom
fix-lock-threads-token

Conversation

@diemol

@diemol diemol commented Oct 6, 2026

Copy link
Copy Markdown
Member

Thanks for contributing to the Selenium IDE!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Bumps dessant/lock-threads from v5 to v6 in .github/workflows/lock.yml. The v6 tag currently points to v6.0.2.

Motivation and Context

The scheduled "Lock Issues" workflow is failing (run) with:

"github-token" length must be less than or equal to 100 characters long

v5 only accepts tokens up to 100 characters, and GitHub's new token format is longer than that. This was fixed upstream in v6.0.2 (dessant/lock-threads#55). The update also clears the Node.js 20 deprecation warning, because v6 runs on Node 24. That's the only breaking change in v6, and no workflow inputs need to change.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • I have read the contributing document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

🤖 Generated with Claude Code

v5 rejects GitHub tokens longer than 100 characters, which breaks with
GitHub's new token format. Fixed upstream in v6.0.2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Bump lock-threads to v6 to accept longer GitHub tokens

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Upgrade the scheduled issue-locking action to v6 to resolve token-length validation failures.
• Retain the existing workflow settings; v6 also runs on Node.js 24.
High-Level Assessment

Use the upstream v6 release, which fixes token validation without requiring workflow input changes. Changing the token or replacing the action would add unnecessary complexity.

Files changed (1) +1 / -1

Bug fix (1) +1 / -1
lock.ymlUpgrade the issue-locking action to v6 +1/-1

Upgrade the issue-locking action to v6

• Changes dessant/lock-threads from v5 to v6 so the scheduled workflow can accept longer GitHub tokens. The issue-locking inputs remain unchanged.

.github/workflows/lock.yml

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@diemol
diemol merged commit b9a7a5f into trunk Oct 6, 2026
1 of 2 checks passed
@diemol
diemol deleted the fix-lock-threads-token branch October 6, 2026 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant