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
Bump pyatv to 0.7.6 #45799
Bump pyatv to 0.7.6 #45799
Conversation
Please add a link to a changelog or GitHub commit compare view for the version bump in the PR description. Thanks! |
I've added the link. 👍 |
You beat me to it! 🚴♂️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
If it's possible to wish, it would be great to have this included in the next release as it fixes a few issues people are having. |
And the other changes are safe, ie don't mean users need to change anything? |
Nah, it's just bug fixes and robustness enhancements in this release. |
Ok, tagged. 👍 |
Just tested and everything appears to be working as expected. I did notice that the mdns processing (https://www.home-assistant.io/integrations/profiler/) is the most expensive operation on an idle instance: |
@bdraco Great catch, can you open an issue in the pyatv project and include the image? |
Proposed change
Upgrade pyatv to 0.7.6 with the following changes (extract from change log):
https://github.com/postlund/pyatv/releases/tag/v0.7.6
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: