github-action
github-action copied to clipboard
Dependency Dashboard
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Pending Approval
These branches will be created by Renovate only once you click their checkbox below.
- [ ] chore(deps): update dependency @semantic-release/github to v11
- [ ] chore(deps): update dependency @types/node to v22
- [ ] chore(deps): update dependency eslint to v9
- [ ] chore(deps): update dependency eslint-plugin-json to v4
- [ ] chore(deps): update dependency npm-run-all2 to v7
- [ ] chore(deps): update typescript-eslint monorepo to v8 (major) (
@typescript-eslint/eslint-plugin,@typescript-eslint/parser) - [ ] 🔐 Create all pending approval PRs at once 🔐
Awaiting Schedule
These updates are awaiting their schedule. Click on a checkbox to get an update now.
- [ ] docs: update references to ghcr.io/renovatebot/renovate to v38.134.0
- [ ] build(deps): lock file maintenance
Pending Status Checks
These updates await pending status checks. To force their creation now, click the checkbox below.
- [ ] chore(deps): update pnpm to v9.12.3
- [ ] chore(deps): update dependency @types/node to v20.17.2
- [ ] chore(deps): update dependency semantic-release to v24.2.0
Detected dependencies
github-actions
.github/workflows/build.yml
actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683wagoid/commitlint-github-action v6.1.2@3d28780bbf0365e29b144e272b2121204d5be5f3actions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683actions/setup-node v4.1.0@39370e3970a6d050c480ffad4ff0ed4d3fdee5afactions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683actions/setup-node v4.1.0@39370e3970a6d050c480ffad4ff0ed4d3fdee5afactions/checkout v4.2.2@11bd71901bbe5b1630ceea73d27597364c9af683actions/setup-node v4.1.0@39370e3970a6d050c480ffad4ff0ed4d3fdee5af
npm
package.json
@actions/core 1.11.1@actions/exec 1.1.1@commitlint/cli 19.5.0@commitlint/config-conventional 19.5.0@semantic-release/git 10.0.1@semantic-release/github 10.3.5@semantic-release/npm 12.0.1@tsconfig/node20 20.1.4@types/node 20.16.14@typescript-eslint/eslint-plugin 6.21.0@typescript-eslint/parser 6.21.0@vercel/ncc 0.38.2conventional-changelog-conventionalcommits 8.0.0eslint 8.57.1eslint-config-prettier 9.1.0eslint-plugin-json 3.1.0husky 9.1.6lint-staged 15.2.10npm-run-all2 6.2.6prettier 3.3.3prettier-plugin-packagejson 2.5.3rimraf 6.0.1semantic-release 24.1.3ts-node 10.9.2typescript 5.6.3node >=20.9.0pnpm ^9.0.0pnpm 9.12.2
regex
README.md
ghcr.io/renovatebot/renovate 38.133.0README.md
actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4actions/checkout v4.2.2renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4.github/workflows/build.yml
renovate 38.134.0README.md
renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4renovatebot/github-action v40.3.4README.md
ghcr.io/renovatebot/renovate 38.133.0ghcr.io/renovatebot/renovate 38.133.0
- [ ] Check this box to trigger a request for Renovate to run again on this repository
@viceice Should "lock file maintenance" be enabled? If so I'll check the checkbox to approve it.
You can approve it, but it will always come back to be un approved after run. We can do lockfile management on manual regular schedule, or if security issues occure, which can be fixed by lockfile maintenance.
So this is just like the rebase checkbox in a PR where you check it once to rebase the PR. I think the lockfile management is only needed when there is a security issue (handled by dependabot if I'm not mistaken). So, we don't need to do anything for it IMHO. Just to check: are security issues enabled for this repository?
actions/setup-node v2 is currently a pre-release