Skip to content

Please consider fixing issues detected by repository checker #131

Description

@ioBroker-Bot

Notification from ioBroker Check and Service Bot

Dear adapter developer,

I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter radiohead for common errors and appropiate suggestions to keep this adapter up to date.

This check is based on the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.radiohead

Downloads Number of Installations (latest) Number of Installations (stable) - Test and Release

ERRORS:

  • ❗ [E0036] @alcalzone/release-script 5.0.0 specified. 5.2.1 is required as minimum, 5.2.1 (or newer) is current. Please update devDependencies at package.json
  • ❗ [E0036] @alcalzone/release-script-plugin-iobroker 4.0.0 specified. 5.2.0 is required as minimum, 5.2.0 (or newer) is current. Please update devDependencies at package.json
  • ❗ [E0036] @alcalzone/release-script-plugin-license 4.0.0 specified. 5.2.0 is required as minimum, 5.2.0 (or newer) is current. Please update devDependencies at package.json
  • ❗ [E0036] @alcalzone/release-script-plugin-manual-review 4.0.0 specified. 5.2.0 is required as minimum, 5.2.0 (or newer) is current. Please update devDependencies at package.json
  • ❗ [E0036] @iobroker/testing 5.1.1 specified. 5.2.2 is required as minimum, 5.2.2 (or newer) is current. Please update devDependencies at package.json
  • ❗ [E3022] "test-and-release.yml": job "deploy" uses node.js 22 which is below the minimum required version 24. Please update to node.js 24.
  • ❗ [E3027] "test-and-release.yml": testing for OS windows, macos is missing in job "adapter-tests". Add corresponding tests to "test-and-release.yml" or adapt package.json "os" accordingly.
  • ❗ [E8004] Please process issue [#103] "Compatibility check and testing for Responsive Design (materialize)"

WARNINGS:

SUGGESTIONS:

  • 📌 [S0062] Consider adding and using package "@iobroker/eslint-config".
  • 📌 [S0071] No devDependency for "@iobroker/eslint-config" found. Consider migrating to the shared ESLint config.
  • 📌 [S0073] "eslint":"^9.39.0" is >= 9.0.0 but "@iobroker/eslint-config" is not used. Consider migrating to "@iobroker/eslint-config".
  • 📌 [S0085] No devDependency "@tsconfig/nodeXX" found. Consider adding one for proper type checking (see ioBroker.examples for examples).
  • 📌 [S0088] "/tsconfig.json" should contain an extends clause like "extends": "@tsconfig/node20/tsconfig.json" (see ioBroker.examples).
  • 📌 [S3021] "test-and-release.yml": job "check-and-lint" uses node.js 22. Consider updating to the recommended version 24.
  • 📌 [S3056] "test-and-release.yml": workflow run #210 on branch "master" is older than 90 days; log files are no longer available.
  • 📌 [S5022] Please consider migrating to admin 5 UI (jsonConfig) or react based UI.
  • 📌 [S8910] File "/.github/workflows/dependabot-auto-merge.yml.OLD" was found. If it is no longer needed, consider deleting it.

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible - at least with next minor release. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository. Priority bugfixes will not be blocked by existing errors as long as tests pass.

Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.

You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:

@iobroker-bot recheck
or
@iobroker-bot recreate

Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.

Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Fri, 31 Jul 2026 09:27:48 GMT based on commit bbdfe70
ioBroker.repochecker 5.19.12

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions