search

jbcom / terraform-github-markdown

Apache License 2.0
0 stars 0 forks source link

chore(deps): update dessant/lock-threads action to v5 #19

Closed renovate[bot] closed 9 months ago

renovate[bot] commented 11 months ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
dessant/lock-threads action major v3 -> v5

Release Notes

dessant/lock-threads (dessant/lock-threads) ### [`v5`](https://togithub.com/dessant/lock-threads/compare/v4...v5) [Compare Source](https://togithub.com/dessant/lock-threads/compare/v4...v5) ### [`v4`](https://togithub.com/dessant/lock-threads/compare/v3...v4) [Compare Source](https://togithub.com/dessant/lock-threads/compare/v3...v4)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

This PR has been generated by Mend Renovate. View repository job log here.

github-actions[bot] commented 10 months ago

This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days

github-actions[bot] commented 9 months ago

This PR was automatically closed because of stale in 10 days

renovate[bot] commented 9 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

github-actions[bot] commented 8 months ago

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.