mirror of
https://github.com/pezkuwichain/phishing.git
synced 2026-10-20 18:56:29 +00:00
@pezkuwi/util, util-crypto and x-fetch now require ^14.0.26, which brings @pezkuwi/wasm-crypto 7.5.20 in place of 7.5.17. The lockfile moves with it. axios moves to ^1.20.0 in resolutions, with the lockfile entries that the Dependabot PR for it (#11) left out; without them `yarn install --immutable` refused to run and every check on that PR failed. Lock Threads has failed on every scheduled run: lock-threads v4 rejects a github-token longer than 100 characters, and GitHub's tokens now are. v6.0.2 fixes the validation. Since v5 the action also locks discussions by default; process-only keeps it to issues and pull requests, as before and as the job's permissions allow.
33 lines
974 B
YAML
33 lines
974 B
YAML
name: 'Lock Threads'
|
|
|
|
on:
|
|
schedule:
|
|
- cron: '10 2/3 * * *'
|
|
|
|
permissions: {}
|
|
|
|
jobs:
|
|
lock:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 10
|
|
permissions:
|
|
issues: write
|
|
pull-requests: write
|
|
env:
|
|
YARN_ENABLE_SCRIPTS: false
|
|
steps:
|
|
- uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2
|
|
with:
|
|
github-token: ${{ github.token }}
|
|
process-only: 'issues, prs'
|
|
issue-inactive-days: '7'
|
|
issue-comment: >
|
|
This thread has been automatically locked since there has not been
|
|
any recent activity after it was closed. Please open a new issue
|
|
if you think you have a related problem or query.
|
|
pr-inactive-days: '2'
|
|
pr-comment: >
|
|
This pull request has been automatically locked since there
|
|
has not been any recent activity after it was closed.
|
|
Please open a new issue for related bugs.
|