Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please consider fixing issues detected by repository checker #412

Open
6 of 8 tasks
ioBroker-Bot opened this issue Sep 11, 2024 · 3 comments
Open
6 of 8 tasks

Please consider fixing issues detected by repository checker #412

ioBroker-Bot opened this issue Sep 11, 2024 · 3 comments

Comments

@ioBroker-Bot
Copy link

ioBroker-Bot commented Sep 11, 2024

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 mydlink 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.mydlink

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

ERRORS:

WARNINGS:

  • 👀 [W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json
  • 👀 [W040] "keywords" within package.json should contain "ioBroker"
  • 👀 [W529] Plugin "manual-review" missing at .releaseconfig.json. Please add.

SUGGESTIONS:

  • 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).
  • 📌 [S526] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".

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

Errors reported by repository checker should be fixed as soon as possible. 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.

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, 27 Dec 2024 04:32:59 GMT based on commit d58e54b
ioBroker.repochecker 3.2.2

@ioBroker-Bot
Copy link
Author

This issue has been updated by ioBroker Check and Service Bot

The following issues are new and have been added
[W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json

@ioBroker-Bot
Copy link
Author

This issue has been updated by ioBroker Check and Service Bot

The following issues are new and have been added
[E804] Please process issue [#413] "Compatibility check and testing for node.js 22"

@ioBroker-Bot
Copy link
Author

This issue has been updated by ioBroker Check and Service Bot

The following issues are new and have been added
[W529] Plugin "manual-review" missing at .releaseconfig.json. Please add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant