Skip to content

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

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/dessant-lock-threads-6.x
Open

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

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Dec 13, 2025 •
edited
Loading

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
Bug Fixes
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
Bug Fixes
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
Bug Fixes
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
Bug Fixes
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.

@auto-assign auto-assign Bot requested a review from AlexRogalskiy December 13, 2025 15:52
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Dec 13, 2025

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

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Dec 13, 2025

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.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Dec 13, 2025

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.

@renovate renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from 48decaf to 7950c8e Compare April 30, 2026 02:01
@renovate renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from 7950c8e to aadebe8 Compare May 13, 2026 02:55
@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 13, 2026 •
edited
Loading

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 High
Obfuscated code: npm braces is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/cz-conventional-changelog@3.3.0 → npm/braces@2.3.2

ℹ 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/braces@2.3.2. 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 High
Obfuscated code: npm cssom is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → 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 High
Obfuscated code: npm doctrine is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.json → npm/eslint-plugin-import@2.22.1 → npm/doctrine@1.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/doctrine@1.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.

View full report

@renovate
⬆️ Updates dessant/lock-threads action to v6
1c1b9f6 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot force-pushed the renovate/dessant-lock-threads-6.x branch from aadebe8 to 1c1b9f6 Compare May 23, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AlexRogalskiy AlexRogalskiy Awaiting requested review from AlexRogalskiy

Assignees

No one assigned

Labels

npm dependencies review-required

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants