feat(zigbee): Update esp-zigbee-lib to 1.6.7 #11772

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

Jump to bottom

Merged

me-no-dev merged 1 commit into master from update-zigbee-sdk-1.6.7

Aug 29, 2025

Merged

feat(zigbee): Update esp-zigbee-lib to 1.6.7 #11772

me-no-dev merged 1 commit into master from update-zigbee-sdk-1.6.7

Aug 29, 2025

Conversation

P-R-O-C-H-Y

Copy link

Member

@P-R-O-C-H-Y P-R-O-C-H-Y commented Aug 29, 2025

Description of Change

This pull request updates the Zigbee-related dependencies to newer versions for improved compatibility. The changes ensure that esp-zboss-lib and esp-zigbee-lib are aligned with their latest compatible releases.

Dependency updates:

Updated esp-zboss-lib version requirement to be compatible with esp-zigbee-lib 1.6.7 in idf_component.yml.
Updated esp-zigbee-lib version from 1.6.6 to 1.6.7 in idf_component.yml.

Test Scenarios

Will be tested with new libs when build.

Related links

@P-R-O-C-H-Y


 feat(zigbee): Update esp-zigbee-lib to newest

cdc46c5

@P-R-O-C-H-Y P-R-O-C-H-Y self-assigned this

Aug 29, 2025

@P-R-O-C-H-Y P-R-O-C-H-Y requested a review from SuGlider as a code owner

August 29, 2025 09:43

@P-R-O-C-H-Y P-R-O-C-H-Y added the Area: Zigbee label

Aug 29, 2025

@P-R-O-C-H-Y P-R-O-C-H-Y requested a review from me-no-dev as a code owner

August 29, 2025 09:43

@github-actions GitHub Actions

Copy link

Contributor

github-actions bot commented Aug 29, 2025

Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello P-R-O-C-H-Y, we appreciate your contribution to this project!

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against cdc46c5