Please consider fixing issues detected by repository checker

ioBroker-Bot commented 3 weeks ago

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 sbfspot for common errors and appropiate suggestions to keep this adapter up to date.

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

Please see the result of the check below.

ioBroker.sbfspot

Number of Installations (latest) Number of Installations (stable) -

ERRORS:

[ ] :heavy_exclamation_mark: [E204] Versions "4.3.0, 4.2.3, 4.2.2" listed at common.news at io-package.json do not exist at NPM. Please remove from news section.

WARNINGS:

[x] :eyes: [W034] @iobroker/adapter-core 3.1.4 specified. 3.1.6 is recommended. Please consider updating dependencies at package.json
[x] :eyes: [W162] js-controller 5.0.0 listed as dependency but 5.0.19 is recommended. Please consider updating dependency at io-package.json.
[x] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[x] :eyes: [W521] "gulp" found at devDependencies at package.json but no "gulpfile.js" found. Is this dependency really required?
[x] :eyes: [W853] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

[x] :pushpin: [S519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
[ ] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).

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 at any time by adding the following comment to this issue:

@iobroker-bot recheck

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

Note: This issue replaces issue #397

@mcm1957 for evidence

rg-engineering commented 2 weeks ago

@iobroker-bot recheck

ioBroker-Bot commented 2 weeks ago

This issue has been replaced by new isse #411
This issue can be closed.

your
ioBroker Check and Service Bot

ioBroker-Bot commented 1 week ago

Thanks for contacting me.
I received your request to recheck this repository. I will start doing my work soon.
I will close an existing issue and create a new one if still any issues are to be evaluated and potentially to be fixed.

Thanks for spending your time and working at an ioBroker adapter.

your
ioBroker Check and Service Bot

ioBroker-Bot commented 1 week ago

Thanks for processing and closing this issue.

I will recheck for new issues later. So it's no problem if this issue has been closed premature.

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

@iobroker-bot recheck

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. Let's work together for the best user experience.
your
ioBroker Check and Service Bot

rg-engineering / ioBroker.sbfspot