Bump zigpy to 1.5.0#275
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #275 +/- ##
=======================================
Coverage 98.49% 98.49%
=======================================
Files 43 43
Lines 3583 3583
=======================================
Hits 3529 3529
Misses 54 54 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We've had multiple recent PRs that target zigpy 1.5.x compatibility. The fixes themselves still work on older versions, but the adjusted tests do not. Before releasing v1.1.0, we bump the zigpy requirement to 1.5.0, since that's what this zigpy-znp version now mainly targets.
Recent PRs:
ZNPCoordinator.request()rejecting new zigpy kwargs #272NWK_NO_ROUTEinsend_packet#273