-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
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
2024.6.3 #119742
Conversation
* Include speech_slots in IntentResponse.as_dict * Populate speech_slots only if available * fix typo * Add test * test all fields * Fix another test --------- Co-authored-by: Paulus Schoutsen <[email protected]>
Co-authored-by: Jan Bouwhuis <[email protected]>
…fallback" (#119526) * Revert "Revert Use integration fallback configuration for tado water heater fallback (#119466)" This reverts commit ade936e. * add decide method for duration * add repair issue to let users know * test module for repairs * Update strings.json Co-authored-by: Franck Nijhof <[email protected]> * repair issue should not be persistent * use issue_registery fixture instead of mocking * fix comment * parameterize repair issue created test case --------- Co-authored-by: Franck Nijhof <[email protected]>
* Bump uiprotect to 1.2.0 changelog: uilibs/uiprotect@v1.1.0...v1.2.0 * bump
* Bump bellows to 0.39.1 * Bump zigpy to 0.64.1
So do we want to cherry-pick the CI pin to Python 3.12.3 into this for now? |
I'm testing pydantic/pydantic#9660 to see if it fixes pydantic .16 but it still won't solve this issue right now since we would have to wait for .17 anyways so pinning back to 12.3 makes sense since its already broken anyways |
after pydantic/pydantic#9660 and the changes I noted in that PR the tests pass in #119430 and uilibs/uiprotect#39 so hopefully we will get a 1.0.17 soon with that change |
Release notes adjustments: home-assistant/home-assistant.io#33285