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

Update synochat to 1.3.2 #4442

Closed
wants to merge 1 commit into from
Closed

Conversation

phoeluga
Copy link
Contributor

@phoeluga phoeluga commented Jan 4, 2025

Please update my adapter ioBroker.synochat to version 1.3.2.

Please update my adapter ioBroker.synochat to version 1.3.2.
@github-actions github-actions bot added Stable auto-checked This PR was automatically checked for obvious criterias labels Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

Automated adapter checker

ioBroker.synochat

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

👍 No errors found

Adapter releases: https://www.iobroker.dev/adapter/synochat/releases
Adapter statistic: https://www.iobroker.dev/adapter/synochat/statistics

History and usage information for release 1.3.2:

1.3.2 created 4.1.2025 (0 days old)
undefined users (NaN%)

1.3.1 (stable) created 13.8.2023 (510 days old)
142 users (stable) (94.67%)

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

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

@mcm1957 mcm1957 added the STABLE - 0-Day PR This PR for stable has been created before release was availabla at latest label Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

ioBroker repository information about STABLE-0-Day-PR tagging

Your PR has been tagged with the label STABLE-0-day-PR. This indicates that the release requested to be added to the stable repository has been created within one day after releasing the new version. Currently this release has not even been published at LATEST repository. So this release is too young for immediate processing.

Normally, a release should be available at LATEST repository for at least one or two weeks without any serious new issues detected within this timeframe. Your PR will be closed for now. Please create a new PR after the new version has been available at LATEST repository for at least one or two weeks, has a considerable number of installations and no serious new issues.

IMPORTANT:
Of course, it is possible to release a new version immediately if it is a hotfix for a serious problem, i.e. some errors cause adapter crashes or incompatible api changes of external websites blocking normal usage. In this case, please indicate this fact as a comment and mention mcm1957 and eventually Apollon77 explicitly. Please describe the reason (i.e. by referencing an issue). Hotfixes should minimize the changes, even dependency updates should be avoided if not related to the fix. New functionality and major (breaking) updates are most likely never a hotfix.

Please note that ANY (even hotfixes) should be available at LATEST repository for at least 1 day and have some (few) installations to avoid hotfixes with serious problems at stable repository. Exceptions to this minimal delay must be discussed individually.

Feel free to contact me (mcm1957) if you have any more questions.

@mcm1957 mcm1957 closed this Jan 4, 2025
@phoeluga phoeluga deleted the patch-1 branch January 4, 2025 21:55
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 STABLE - 0-Day PR This PR for stable has been created before release was availabla at latest Stable
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants