renovatebot
Dependency Dashboard
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.
Deprecations / Replacements
[!WARNING] These dependencies are either deprecated or have replacements available:
| Datasource | Name | Replacement PR? |
|---|---|---|
| npm | @tsconfig/node20 |
 |
[!NOTE] These dependencies have not received updates for an extended period and may be unmaintained:
View abandoned dependencies (3)
| Datasource | Name | Last Updated |
|---|---|---|
| npm | @semantic-release/git |
2021-10-30 |
| npm | eslint-plugin-json |
2024-08-07 |
| npm | husky |
2024-11-18 |
Packages are marked as abandoned when they exceed the abandonmentThreshold since their last release.
Unlike deprecated packages with official notices, abandonment is detected by release inactivity.
Pending Approval
The following branches are pending approval. To create them, click on a checkbox below.
- [ ] chore(deps): update dependency @types/node to v22
- [ ] fix(deps): update dependency @actions/core to v2
- [ ] fix(deps): update dependency @actions/exec to v2
- [ ] 🔐 Create all pending approval PRs at once 🔐
Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- [ ] docs: update references to ghcr.io/renovatebot/renovate to v42.64.1
- [ ] docs: update references to renovatebot/github-action to v44.2.0
- [ ] build(deps): lock file maintenance
- [ ] 🔐 Create all awaiting schedule PRs at once 🔐
Pending Status Checks
The following updates await pending status checks. To force their creation now, click on a checkbox below.
- [ ] chore(deps): replace dependency @tsconfig/node20 with @tsconfig/node22
- [ ] chore(deps): update dependency esbuild to v0.27.2
- [ ] chore(deps): update dependency typescript-eslint to v8.50.0
- [ ] chore(deps): update pnpm to v10.26.1
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- [ ] chore(deps): update dependency @tsconfig/strictest to v2.0.8
- [ ] chore(deps): update dependency @types/node to v24
- [ ] Click on this checkbox to rebase all open PRs at once
Detected Dependencies
github-actions (2)
.github/actions/setup-node/action.yml (4)
actions/cache v5.0.1@9255dc7a253b0ccc959486e2bca901246202afebpnpm/action-setup v4.2.0@41ff72655975bd51cab0327fa583b6e92b6d3061actions/setup-node v6.1.0@395ad3262231945c25e8478fd5baf05154b1d79factions/cache v5.0.1@9255dc7a253b0ccc959486e2bca901246202afeb.github/workflows/build.yml (8)
actions/checkout v6.0.1@8e8c483db84b4bee98b60c0593521ed34d9990e8actions/checkout v6.0.1@8e8c483db84b4bee98b60c0593521ed34d9990e8wagoid/commitlint-github-action v6.2.1@b948419dd99f3fd78a6548d48f94e3df7f6bf3edactions/checkout v6.0.1@8e8c483db84b4bee98b60c0593521ed34d9990e8actions/checkout v6.0.1@8e8c483db84b4bee98b60c0593521ed34d9990e8actions/checkout v6.0.1@8e8c483db84b4bee98b60c0593521ed34d9990e8actions/checkout v6.0.1@8e8c483db84b4bee98b60c0593521ed34d9990e8ghcr.io/renovatebot/renovate 42.64.1@sha256:e09f71019881fff15f397560d979736c6c6fd712f790fdb0a75697a324ee965a
nodenv (1)
.node-version (1)
node 24.12.0
npm (2)
example/package.json
package.json (30)
@actions/core 1.11.1@actions/exec 1.1.1@commitlint/cli 20.2.0@commitlint/config-conventional 20.2.0@eslint/js 9.39.2@semantic-release/git 10.0.1@semantic-release/github 12.0.2@semantic-release/npm 13.1.3@tsconfig/node20 20.1.8@tsconfig/strictest 2.0.6@types/eslint-config-prettier 6.11.3@types/node 20.19.27conventional-changelog-conventionalcommits 9.1.0esbuild 0.27.1eslint 9.39.2eslint-config-prettier 10.1.8eslint-plugin-json 4.0.1globals 16.5.0husky 9.1.7lint-staged 16.2.7npm-run-all2 8.0.4prettier 3.7.4prettier-plugin-packagejson 2.5.20rimraf 6.1.2semantic-release 25.0.2typescript 5.9.3typescript-eslint 8.49.0node ^20.9.0 || ^22.11.0 || ^24.11.0pnpm ^10.0.0pnpm 10.25.0
regex (7)
.github/workflows/build.yml (1)
renovate 42.64.1action.yml (1)
ghcr.io/renovatebot/renovate 42README.md (1)
ghcr.io/renovatebot/renovate 42.52.8README.md (24)
actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0actions/checkout v6.0.1renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0README.md (14)
renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0renovatebot/github-action v44.1.0README.md (2)
ghcr.io/renovatebot/renovate 42.52.8ghcr.io/renovatebot/renovate 42.52.8src/docker.ts (1)
ghcr.io/renovatebot/renovate 42
renovate-config-presets (1)
.github/renovate.json
- [ ] Check this box to trigger a request for Renovate to run again on this repository
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
@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?