azu / azu/ts-node-test-register
Dependency Dashboard
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/azu/ts-node-test-register).
## Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- [ ] [chore(deps): update actions/checkout action to v7](../pull/93)
- [ ] [chore(deps): update actions/setup-node action to v7](../pull/94)
- [ ] [chore(deps): update dependency cross-env to v10](../pull/84)
- [ ] [chore(deps): update dependency lint-staged to v17](../pull/92)
- [ ] [chore(deps): update dependency mocha to v12](../pull/96)
- [ ] [fix(deps): update dependency read-pkg to v10](../pull/89)
- [ ] **Click on this checkbox to rebase all open PRs at once**
## Detected Dependencies
github-actions (1)
.github/workflows/test.yml (3)
- `actions/checkout v4.4.0@11d5960a326750d5838078e36cf38b85af677262` → [Updates: `v7.0.1`]
- `actions/setup-node v4.4.0@49933ea5288caeca8642d1e84afbd3f7d6820020` → [Updates: `v7.0.0`]
- `node ${{ matrix.node-version }}`
npm (2)
example/package.json (3)
- `expected-exit-status ^3.1.0`
- `mocha ^11.8.0` → [Updates: `^12.0.0`]
- `ts-node ^10.9.2`package.json (8)
- `read-pkg ^5.2.0` → [Updates: `^10.1.0`]
- `@types/mocha ^10.0.10`
- `@types/node ^18.19.130` → [Updates: `^24.13.4`]
- `cross-env ^7.0.3` → [Updates: `^10.1.0`]
- `lint-staged ^13.3.0` → [Updates: `^17.5.1`]
- `mocha ^11.8.0` → [Updates: `^12.0.0`]
- `ts-node ^10.9.2`
- `ts-node ^10.9.2`
renovate-config (1)
renovate.json
---
- [ ] Check this box to trigger a request for Renovate to run again on this repository
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the dependency entries in .github/workflows/test.yml, package.json, example/package.json, and renovate.json. Start by checking the listed update pull requests and their status; done means the open dependency updates have been handled and the dashboard no longer lists them as pending.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- devops, testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100