nf-core / nf-core/setup-nf-test
Renovate Dashboard 🤖
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
Abandoned Dependencies
The following dependencies have not received updates for an extended period and may be unmaintained.
View abandoned dependencies (3)
[!NOTE]
Packages are marked as abandoned when they exceed theabandonmentThresholdsince their last release. Unlike deprecated packages with official notices, abandonment is detected by release inactivity.
| Datasource | Package | Last Updated |
|---|---|---|
| github-actions | JasonEtco/build-and-tag-action | 2022-12-21 |
| npm | fast-diff | 2023-05-19 |
| npm | husky | 2024-11-18 |
Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- Update dependency @vercel/ncc to v0.45.0
- Update dependency lint-staged to v17.3.0
- 🔐 Create all awaiting schedule PRs at once 🔐
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- Update dependency prettier to v3.9.6
- Update GitHub Actions (
actions/checkout,actions/setup-java,actions/setup-node,nf-core/setup-nextflow) - Update dependency @actions/cache to v6.2.0
- Update dependency fs-extra to v11.4.0
- Update actions/setup-node action to v7
- Lock file maintenance
- Click on this checkbox to rebase all open PRs at once
Detected Dependencies
github-actions (2)
.github/workflows/main.yml (5)
actions/checkout v7.0.0@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0→ [Updates:v7.0.1]actions/setup-node v6.4.0@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e→ [Updates:v6.5.0,v7.0.0]actions/setup-java v5.4.0@1bcf9fb12cf4aa7d266a90ae39939e61372fe520→ [Updates:v5.7.0]nf-core/setup-nextflow v3.0.0@b4ec1bc7c16a94435159de94a05253542fddf6ef→ [Updates:v3.0.1]node 24.github/workflows/publish.yml (4)
actions/checkout v7.0.0@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0→ [Updates:v7.0.1]actions/setup-node v6.4.0@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e→ [Updates:v6.5.0,v7.0.0]JasonEtco/build-and-tag-action v2@dd5e4991048c325f6d85b4155e586fc211c644danode 24
npm (1)
package.json (11)
@actions/cache ^6.0.0→ [Updates:^6.0.0]@actions/core ^3.0.1@actions/exec ^3.0.0@actions/io ^3.0.2@actions/tool-cache ^4.0.0fast-diff ^1.3.0fs-extra ^11.3.4→ [Updates:^11.3.4]@vercel/ncc 0.44.1→ [Updates:0.45.0]husky 9.1.7lint-staged 17.0.8→ [Updates:17.3.0]prettier 3.9.4→ [Updates:3.9.6]
renovate-config (1)
.github/renovate.json5
- Check this box to trigger a request for Renovate to run again on this repository
Contributor guide
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.
Research direction
Review .github/workflows/main.yml, .github/workflows/publish.yml, package.json, and .github/renovate.json5, starting with the awaiting-schedule updates and linked pull requests. Use the Renovate dashboard to identify which updates remain actionable; done means the selected dependency updates are validated and their corresponding pull requests are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100