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 zigbee to 1.8.25 #3086

Merged
merged 1 commit into from
Dec 24, 2023
Merged

Update zigbee to 1.8.25 #3086

merged 1 commit into from
Dec 24, 2023

Conversation

arteck
Copy link
Contributor

@arteck arteck commented Dec 19, 2023

No description provided.

@github-actions github-actions bot added auto-checked This PR was automatically checked for obvious criterias Stable labels Dec 19, 2023
@mcm1957 mcm1957 changed the title zigbee new Update zigbee to 1.8.25 Dec 19, 2023
Copy link

Automated adapter checker

ioBroker.zigbee

Downloads Number of Installations (latest) Number of Installations (stable)
NPM

👍 No errors found

  • 👀 [W156] Adapter should support admin 5 UI (jsonConfig) if you do not use a React based UI
  • 👀 [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package

Adapter releases: https://www.iobroker.dev/adapter/zigbee/releases

Adapter statistic: https://www.iobroker.dev/adapter/zigbee/statistics

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

@mcm1957
Copy link
Collaborator

mcm1957 commented Dec 19, 2023

1.8.25 created 17.12.2023
400 user (2%)

Copy link

ioBroker repository information about STABLE-BRAND-NEW tagging

Your PR has been tagged with the label STABLE - BRAND NEW. This indicates that the release requested to be added to the stable repository seems to be too young for immediate processing.

Normally, a release should be available at LATEST repository for at least one or two weeks without any serious issues detected within this timeframe. Your release seems to be younger than 7 days.Your PR will be kept in evidence and will be merged approximately one week after creation of the release without any further action required by you.

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.

@github-actions github-actions bot added the ⚠️check Issue/PR needs attention label Dec 24, 2023
@mcm1957 mcm1957 removed the ⚠️check Issue/PR needs attention label Dec 24, 2023
@mcm1957 mcm1957 merged commit 7c84a3a into ioBroker:master Dec 24, 2023
12 checks passed
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants