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 #235

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

Please consider fixing issues detected by repository checker #235

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

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

👍 No errors found

WARNINGS:

  • 👀 [W034] @iobroker/adapter-core 3.2.1 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json
  • 👀 [W156] js-controller 4.0.24 listed as dependency but 5.0.19 is recommended. Please consider updating dependency at io-package.json.
  • 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
  • 👀 [W951] .npmignore found but "files" is used at package.json. Please remove .npmignore.

SUGGESTIONS:

  • 📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

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

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, 06 Dec 2024 10:32:07 GMT based on commit da3e9d7
ioBroker.repochecker 3.2.2

@ioBroker-Bot
Copy link
Author

This issue has been updated by ioBroker Check and Service Bot

The following issues have been fixed
[E951] .npmignore found but "files" is used at package.json. Please remove .npmignore.

👍Thanks for fixing the issues.

The following issues are new and have been added
[W951] .npmignore found but "files" is used at package.json. Please remove .npmignore.

@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.2.1 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 have been fixed
[W034] @iobroker/adapter-core 3.2.1 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json

👍Thanks for fixing the issues.

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