Bump zigpy-znp from 1.0.0 to 1.1.0

[dependabot]

Bumps zigpy-znp from 1.0.0 to 1.1.0.

Release notes

Sourced from zigpy-znp's releases.

v1.1.0

What's Changed

• Fix ZNPCoordinator.request() rejecting new zigpy kwargs by @​TheJulianJES in zigpy/zigpy-znp#272
• Remove obsolete retrying patch from tests by @​TheJulianJES in zigpy/zigpy-znp#274
• Retry after route rediscovery on NWK_NO_ROUTE in send_packet by @​TheJulianJES in zigpy/zigpy-znp#273
• Bump zigpy to 1.5.0 by @​TheJulianJES in zigpy/zigpy-znp#275

Full Changelog: zigpy/zigpy-znp@v1.0.0...v1.1.0

Commits

• 614f74e Bump zigpy to 1.5.0 (#275)
• 2ca6864 Retry after route rediscovery on NWK_NO_ROUTE in send_packet (#273)
• 09d5466 Remove obsolete retrying patch from tests (#274)
• fb6f613 Fix ZNPCoordinator.request() rejecting new zigpy kwargs (#272)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[TheJulianJES]

"Cache save failed" for 3.14 because:
"Failed to save: Unable to reserve cache with key 2-Linux-base-venv-3.14.5-1f5219239464bf9e699ef45497bdb57b851ed987d7f369abbe3282aa80ccd4d6, another job may be creating this cache.".

I don't know why this happens occasionally but the cache key is now blocked for 24 hours IIRC. It can't be removed via the UI or CLI. I'll wait a bit and then retry. Otherwise, I'll lower the CACHE_VERSION in this repo's CI to 1 again.

[TheJulianJES]

Oh, it happened because the first workflow attempt got cancelled – the dependency wasn't available for 3.13 yet, but 3.14 had already found it and was in the cache-saving step. That got cancelled mid-way, so now it's stuck in a reserved but unpopulated state. That seems like something we should try and prevent in our workflow.

I think we can just either add fail-fast: false to the strategy, or add always() to the caching steps. The latter prevents cancellation but we'd also have to check if the previous steps succeeded.

• EDIT: See Protect base venv cache save against cancellation workflows#36.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.41%. Comparing base (3adff2c) to head (e11165a).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #774   +/-   ##
=======================================
  Coverage   97.41%   97.41%           
=======================================
  Files          50       50           
  Lines       10419    10419           
=======================================
  Hits        10150    10150           
  Misses        269      269           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[TheJulianJES]

@dependabot recreate

[dependabot]

The dependabot.yml entry that created this PR has been deleted so this PR can't be recreated. Please close the PR so Dependabot can create a new one with the current dependabot.yml.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[TheJulianJES]

Superseded by:

• Bump zigpy-znp from 1.0.0 to 1.1.0 #779