:arrow_up: Updates dessant/lock-threads action to v6 by renovate[bot] · Pull Request #1183 · AlexRogalskiy/proverbs

renovate · 2025-12-12T20:55:57Z

This PR contains the following updates:

Package	Type	Update	Change
dessant/lock-threads	action	major	`v2.0.3` → `v6.0.2`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

dessant/lock-threads (dessant/lock-threads)

`v6.0.2`

Compare Source

Learn more about this release from the changelog.

`v6.0.1`

Compare Source

Learn more about this release from the changelog.

`v6.0.0`

Compare Source

Learn more about this release from the changelog.

`v6`

Compare Source

`v5.0.1`

Compare Source

Learn more about this release from the changelog.

`v5.0.0`

Compare Source

Learn more about this release from the changelog.

`v5`

Compare Source

⚠ BREAKING CHANGES

Discussions are also processed by default,
set the process-only input parameter to preserve the old behavior

    steps:
      - uses: dessant/lock-threads@v5
        with:
          process-only: 'issues, prs'

the action now requires Node.js 20

Features

lock discussions (0a0976f), closes #25

Bug Fixes

update dependencies (5a25b54)

4.0.1 (2023-06-12)

Bug Fixes

retry and throttle GitHub API requests (1618e91), closes #35

`v4.0.1`

Compare Source

⚠ BREAKING CHANGES

Discussions are also processed by default,
set the process-only input parameter to preserve the old behavior

    steps:
      - uses: dessant/lock-threads@v5
        with:
          process-only: 'issues, prs'

the action now requires Node.js 20

Features

lock discussions (0a0976f), closes #25

Bug Fixes

update dependencies (5a25b54)

4.0.1 (2023-06-12)

Bug Fixes

retry and throttle GitHub API requests (1618e91), closes #35

`v4.0.0`

Compare Source

⚠ BREAKING CHANGES

Discussions are also processed by default,
set the process-only input parameter to preserve the old behavior

    steps:
      - uses: dessant/lock-threads@v5
        with:
          process-only: 'issues, prs'

the action now requires Node.js 20

Features

lock discussions (0a0976f), closes #25

Bug Fixes

update dependencies (5a25b54)

4.0.1 (2023-06-12)

Bug Fixes

retry and throttle GitHub API requests (1618e91), closes #35

`v4`

Compare Source

⚠ BREAKING CHANGES

Discussions are also processed by default,
set the process-only input parameter to preserve the old behavior

    steps:
      - uses: dessant/lock-threads@v5
        with:
          process-only: 'issues, prs'

the action now requires Node.js 20

Features

lock discussions (0a0976f), closes #25

Bug Fixes

update dependencies (5a25b54)

4.0.1 (2023-06-12)

Bug Fixes

retry and throttle GitHub API requests (1618e91), closes #35

`v3.0.0`

Compare Source

Learn more about this release from the changelog.

`v3`

Compare Source

`v2.1.2`

Compare Source

⚠ BREAKING CHANGES

input parameter names have changed

Rename the following input parameters when upgrading from v2 to v3:
- issue-lock-inactive-days --> issue-inactive-days
- issue-exclude-created-before --> exclude-issue-created-before
- issue-exclude-labels --> exclude-any-issue-labels
- issue-lock-labels --> add-issue-labels
- issue-lock-comment --> issue-comment
- pr-lock-inactive-days --> pr-inactive-days
- pr-exclude-created-before --> exclude-pr-created-before
- pr-exclude-labels --> exclude-any-pr-labels
- pr-lock-labels --> add-pr-labels
- pr-lock-comment --> pr-comment

Features

add new filtering and labeling options, update input parameter names (26fd836)
allow manual triggering (a0c7da3)

2.1.2 (2021-08-17)

Bug Fixes

ignore error when commenting on issue converted to discussion (60d2a1a), closes #24

2.1.1 (2021-07-09)

Bug Fixes

update GitHub API calls (a3ccc71)

`v2.1.1`

Compare Source

⚠ BREAKING CHANGES

input parameter names have changed

Rename the following input parameters when upgrading from v2 to v3:
- issue-lock-inactive-days --> issue-inactive-days
- issue-exclude-created-before --> exclude-issue-created-before
- issue-exclude-labels --> exclude-any-issue-labels
- issue-lock-labels --> add-issue-labels
- issue-lock-comment --> issue-comment
- pr-lock-inactive-days --> pr-inactive-days
- pr-exclude-created-before --> exclude-pr-created-before
- pr-exclude-labels --> exclude-any-pr-labels
- pr-lock-labels --> add-pr-labels
- pr-lock-comment --> pr-comment

Features

add new filtering and labeling options, update input parameter names (26fd836)
allow manual triggering (a0c7da3)

2.1.2 (2021-08-17)

Bug Fixes

ignore error when commenting on issue converted to discussion (60d2a1a), closes #24

2.1.1 (2021-07-09)

Bug Fixes

update GitHub API calls (a3ccc71)

`v2.1.0`

Compare Source

⚠ BREAKING CHANGES

input parameter names have changed

Rename the following input parameters when upgrading from v2 to v3:
- issue-lock-inactive-days --> issue-inactive-days
- issue-exclude-created-before --> exclude-issue-created-before
- issue-exclude-labels --> exclude-any-issue-labels
- issue-lock-labels --> add-issue-labels
- issue-lock-comment --> issue-comment
- pr-lock-inactive-days --> pr-inactive-days
- pr-exclude-created-before --> exclude-pr-created-before
- pr-exclude-labels --> exclude-any-pr-labels
- pr-lock-labels --> add-pr-labels
- pr-lock-comment --> pr-comment

Features

add new filtering and labeling options, update input parameter names (26fd836)
allow manual triggering (a0c7da3)

2.1.2 (2021-08-17)

Bug Fixes

ignore error when commenting on issue converted to discussion (60d2a1a), closes #24

2.1.1 (2021-07-09)

Bug Fixes

update GitHub API calls (a3ccc71)

Configuration

📅 Schedule: (in timezone Europe/Moscow)

Branch creation
- "after 10pm every weekday,before 5am every weekday,every weekend"
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

github-actions · 2025-12-12T20:56:38Z

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

github-actions · 2025-12-12T20:56:53Z

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

github-actions · 2025-12-12T20:56:54Z

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

socket-security · 2026-05-23T06:02:55Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `cheerio` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/markdown-link-check@3.14.2` → `npm/cheerio@1.2.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cheerio@1.2.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `cssom` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/jest@27.5.1` → `npm/cssom@0.3.8` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cssom@0.3.8`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `cssom` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/jest@27.5.1` → `npm/cssom@0.4.4` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cssom@0.4.4`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `damerau-levenshtein` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/eslint-plugin-github@4.10.2` → `npm/damerau-levenshtein@1.0.8` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/damerau-levenshtein@1.0.8`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `diff-sequences` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@types/jest@27.5.2` → `npm/jest@27.5.1` → `npm/jest-circus@27.5.1` → `npm/diff-sequences@27.5.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/diff-sequences@27.5.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `entities` is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: `?` → `npm/markdown-link-check@3.14.2` → `npm/entities@4.5.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/entities@4.5.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `entities` is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: `?` → `npm/markdown-link-check@3.14.2` → `npm/entities@6.0.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/entities@6.0.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `htmlparser2` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/markdown-link-check@3.14.2` → `npm/htmlparser2@10.1.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/htmlparser2@10.1.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `kind-of` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/conventional-changelog-cli@2.2.2` → `npm/del-cli@4.0.1` → `npm/@semantic-release/release-notes-generator@9.0.3` → `npm/kind-of@6.0.3` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/kind-of@6.0.3`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

renovate Bot added the npm dependencies label Dec 12, 2025

auto-assign Bot requested a review from AlexRogalskiy December 12, 2025 20:56

vercel Bot had a problem deploying to Preview December 12, 2025 20:56 Failure

github-actions Bot added the review-required label Dec 12, 2025

renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from 17f455c to 3bb9c81 Compare April 23, 2026 14:11

vercel Bot had a problem deploying to Preview April 23, 2026 14:11 Failure

renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from 3bb9c81 to 4061dd5 Compare May 12, 2026 14:34

vercel Bot had a problem deploying to Preview May 12, 2026 14:34 Failure

renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from 4061dd5 to 5fa72e5 Compare May 21, 2026 13:38

vercel Bot had a problem deploying to Preview May 21, 2026 13:38 Failure

⬆️ Updates dessant/lock-threads action to v6

6d3dd5f

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from 5fa72e5 to 6d3dd5f Compare May 23, 2026 06:02

vercel Bot had a problem deploying to Preview May 23, 2026 06:02 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

⬆️ Updates dessant/lock-threads action to v6#1183

⬆️ Updates dessant/lock-threads action to v6#1183
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/dessant-lock-threads-6.x

renovate Bot commented Dec 12, 2025 •

edited

Loading

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

socket-security Bot commented May 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Dec 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

⚠ BREAKING CHANGES

Features

Bug Fixes

4.0.1 (2023-06-12)

Bug Fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

4.0.1 (2023-06-12)

Bug Fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

4.0.1 (2023-06-12)

Bug Fixes

⚠ BREAKING CHANGES

Features

Bug Fixes

4.0.1 (2023-06-12)

Bug Fixes

⚠ BREAKING CHANGES

Features

2.1.2 (2021-08-17)

Bug Fixes

2.1.1 (2021-07-09)

Bug Fixes

⚠ BREAKING CHANGES

Features

2.1.2 (2021-08-17)

Bug Fixes

2.1.1 (2021-07-09)

Bug Fixes

⚠ BREAKING CHANGES

Features

2.1.2 (2021-08-17)

Bug Fixes

2.1.1 (2021-07-09)

Bug Fixes

Configuration

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot commented Dec 12, 2025

Uh oh!

github-actions Bot commented Dec 12, 2025

Hello from PR Helper

Uh oh!

socket-security Bot commented May 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Dec 12, 2025 •

edited

Loading