Dependency Dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github-actions, javascript
Research direction
Start with the Renovate Dependency Dashboard and inspect .github/workflows/nodejs.yml and package.json, along with the linked dependency PRs. Done means the listed dependency updates are reviewed and handled, or the dashboard is otherwise cleared; this issue is stale and mostly automated rather than a defined code change.
Written by the indexing model from the issue text.
Description
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.
Config Migration Needed
- Select this checkbox to let Renovate create an automated Config Migration PR.
Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- chore(deps): lock file maintenance
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- chore(deps): update dependency @vercel/ncc to ^0.45.0
- chore(deps): update actions/checkout action to v7
- Click on this checkbox to rebase all open PRs at once
Detected Dependencies
github-actions (1)
.github/workflows/nodejs.yml (2)
actions/checkout v6→ [Updates:v7]actions/checkout v6→ [Updates:v7]
npm (1)
package.json (3)
@actions/core ^3.0.0@vercel/ncc ^0.38.0→ [Updates:^0.45.0]prettier ^3.0.0
- Check this box to trigger a request for Renovate to run again on this repository
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 3
- Avg merge
- 2h 3m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
data
Difficulty 1/5 Under an hour Newbie friendliness 74/100
gaseous-project/hasheous#637 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
gramps-project/gramps-web#1549 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
change request evaluating
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sindresorhus/eslint-plugin-unicorn#3907 ·
Maintainers usually reply within 1 day
-
Priority: Low Production Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
GrottoCenter/grottocenter-api#1903 ·
Maintainers usually reply within 1 day