Fix unsatisfiable test dependencies conflicting with pytest-homeassistant-custom-component#249
Merged
Merged
Conversation
Copilot created this pull request from a session on behalf of
timlaing
June 30, 2026 19:56
View session
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
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.
Dependabot bumped several test dependency minimums in
requirements_dev.txtabove the exact versions pinned bypytest-homeassistant-custom-component(phcc), making the dependency graph unsatisfiable on Python 3.14 CI.Root cause
phcc pins exact versions of its test stack. The bumped
>=lower bounds exceeded what phcc actually provides, causinguvto find no valid resolution:coverage>=7.14.3>=7.6.8==7.14.0pytest>=8.4.2>=8.3.4==9.0.3pytest-asyncio>=1.4.0>=0.24.0==1.3.0pytest-cov>=7.1.0>=6.0.0==7.1.0The lower bounds are set to the minimum that allows phcc's pinned versions to satisfy them, so future phcc updates will continue to resolve cleanly.