Skip to content

Update plenticore-g3 to 0.1.1 #4778

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

Merged
merged 1 commit into from
May 9, 2025

Conversation

FernetMenta
Copy link
Contributor

Please update my adapter ioBroker.plenticore-g3 to version 0.1.1.

This pull request was created by https://www.iobroker.dev 20f0116.

@github-actions github-actions bot added Stable new at STABLE auto-checked This PR was automatically checked for obvious criterias labels May 8, 2025
Copy link

github-actions bot commented May 8, 2025

Automated adapter checker

ioBroker.plenticore-g3

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

👍 No errors found

Adapter releases: https://www.iobroker.dev/adapter/FernetMenta/ioBroker.plenticore-g3/releases
Adapter statistic: https://www.iobroker.dev/adapter/FernetMenta/ioBroker.plenticore-g3/statistics

History and usage information for release 0.1.1:

0.1.1 created 7.4.2025 (30 days old)
6 users (100.00%)

stable release not yet available

Please verify that this PR really tries to update to release 0.1.1!

ioBroker.refoss

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

👍 No errors found

  • 👀 [S184] "common.singletonHost" detected for non onlyWWW adapter. Is this really desired?

Adapter releases: https://www.iobroker.dev/adapter/Refoss/ioBroker.refoss/releases
Adapter statistic: https://www.iobroker.dev/adapter/Refoss/ioBroker.refoss/statistics

History and usage information for release 0.1.11:

0.1.11 created 23.4.2025 (14 days old)
4 users (33.33%)

0.1.11 (stable) created 23.4.2025 (14 days old)
4 users (stable) (33.33%)

Please verify that this PR really tries to update to release 0.1.11!

Add comment "RE-CHECK!" to start check anew

@FernetMenta
Copy link
Contributor Author

Where does "common.singletonHost detected" come from?

@github-actions github-actions bot added the *📬 a new comment has been added label May 8, 2025
@mcm1957 mcm1957 removed the *📬 a new comment has been added label May 9, 2025
@mcm1957
Copy link
Collaborator

mcm1957 commented May 9, 2025

Where does "common.singletonHost detected" come from?

from checking refoss

@mcm1957 mcm1957 merged commit b40ca26 into ioBroker:master May 9, 2025
10 checks passed
@mcm1957
Copy link
Collaborator

mcm1957 commented May 9, 2025

Your Adapter has been added to stable repository. If you like you can extend the news message here:

https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/history/history.md

If you add some more information / description, please consider to add this information to README.md too.

If you have any questions related to the news file, please contact @Apollon77 for further information.

Please note, that the PR announcing the new adapter at stable might not be merged.
https://github.com/ioBroker/ioBroker.docs/pull/

@FernetMenta
Copy link
Contributor Author

Where does "common.singletonHost detected" come from?

from checking refoss

I mean I am not aware that this adapter is singletonHost. I don't think it is desired. What makes it a singleton and how can I change it? "common.singletonHost" isn't set anywhere.

@github-actions github-actions bot added the *📬 a new comment has been added label May 9, 2025
@mcm1957
Copy link
Collaborator

mcm1957 commented May 9, 2025

Nothing to change.
Please see th location of the log. It does not refer to your adapter :-)

@mcm1957 mcm1957 removed the *📬 a new comment has been added label May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-checked This PR was automatically checked for obvious criterias new at STABLE Stable
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants