Skip to content
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.1.4 #108379

Merged
merged 29 commits into from
Jan 19, 2024
Merged

2024.1.4 #108379

merged 29 commits into from
Jan 19, 2024

Conversation

frenck
Copy link
Member

@frenck frenck commented Jan 19, 2024

Docs PR: home-assistant/home-assistant.io#30937

PaarthShah and others added 28 commits January 19, 2024 15:13
* Skip disk types in System Monitor

* change back
Fix duplicate unique id in System Monitor
* update sleep period for Shelly devices with buggy fw

* code quality

* update model list

* add test

* Apply review comments

* fix test

* use costant
…mes (#107963)

* Reload only a single time when the connection is lost multiple times

* Ignore when reset task finishes, allow only one reset per `ZHAGateway`
* Fix Shelly Gen1 entity description restore

* Update tests/components/shelly/test_sensor.py

Co-authored-by: J. Nick Koston <[email protected]>

---------

Co-authored-by: J. Nick Koston <[email protected]>
* Limit concurrency of startup traffic to allow for interactive usage

* Drop `retryable_req`, we already have request retrying

* Oops, `min` -> `max`

* Add a comment describing why `async_initialize` is not concurrent

* Fix existing unit tests

* Break out fetching mains state into its own function to unit test
Flipr-api version update for resolution of issue #105778
@home-assistant home-assistant bot added cla-signed core merging-to-master This PR is merging into the RC branch and should probably change the branch to `dev`. labels Jan 19, 2024
@joostlek
Copy link
Member

joostlek commented Jan 19, 2024

Failure caused by #108134

cc @allenporter

@allenporter
Copy link
Contributor

Failure caused by #108134

cc @allenporter

It looks like that PR depends on a new API added in #107590 coincidentally? The conservative thing to do can be to drop this change from the release as i'm not sure that trying to roll forward and pull in other refactoring PRs is worth it.

@frenck frenck marked this pull request as draft January 19, 2024 18:23
@frenck
Copy link
Member Author

frenck commented Jan 19, 2024

Will drop that PR from the patch release 👍 That is the safest and most logical way forward.

../Frenck

@frenck frenck marked this pull request as ready for review January 19, 2024 19:20
@frenck frenck merged commit 6e6a5ff into master Jan 19, 2024
101 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jan 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-signed core merging-to-master This PR is merging into the RC branch and should probably change the branch to `dev`.
Projects
None yet
Development

Successfully merging this pull request may close these issues.