Dependency Dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start with .github/workflows/fhem_test.yml, .github/workflows/perlCritic.yml, and .github/workflows/update_controls.yml, comparing each listed dependency with its requested version. Use the Dependency Dashboard controls or update the workflow references, then verify the affected GitHub Actions workflows run successfully and the scheduled updates are addressed.
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.
Awaiting Schedule
The following updates are awaiting their schedule. To get an update now, click on a checkbox below.
- Update shogo82148/actions-setup-perl action to v1.44.2
- Update actions/checkout action to v7
- Update actions/github-script action to v9
- Update fhem/fhem-controls-actions action to v4
- 🔐 Create all awaiting schedule PRs at once 🔐
Detected Dependencies
github-actions (3)
.github/workflows/fhem_test.yml (3)
actions/checkout v6→ [Updates:v7]shogo82148/actions-setup-perl v1.38.1→ [Updates:v1.44.2]fhem/setup-fhem v1.0.1.github/workflows/perlCritic.yml (3)
actions/checkout v6→ [Updates:v7]shogo82148/actions-setup-perl v1.38.1→ [Updates:v1.44.2]reviewdog/action-setup v1.github/workflows/update_controls.yml (4)
actions/checkout v6→ [Updates:v7]fhem/fhem-controls-actions v3.0.1→ [Updates:v4.0.2]fhem/fhem-controls-actions v3.0.1→ [Updates:v4.0.2]actions/github-script v8→ [Updates:v9]
- Check this box to trigger a request for Renovate to run again on this repository
- Dominant language
- Perl
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
convos-chat/convos#977 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
inverse-inc/packetfence#9387 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
linux-test-project/lcov#552 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
szTheory/exifcleaner#383 ·
Maintainers usually reply within 1 day
-
1.severity: security
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NixOS/nixpkgs#569828 · 1 reaction ·
Maintainers usually reply within 1 day