Remove hard pinning requirement from manifest.json #165
Conversation
This file contains 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.
I suggest to remove library "hard-pinning" in
manifest.jsonwebsocket-clientv0.56.0 is very old version and v0.58.0 also include a breaking change, that anyway do not impact this component. We can leave this as mininum version but allow new one to not impact installation of other integrationwakeonlanis on version 2.0.0 in HA. Not big changes, just bug fix, better to set v2.x as minimumnumpyis on version 1.21.1 in HA, but we know that 1.19.2 here is ok, so I would leave 1.19.2 as min but allow new version as done forwebsocket-clientI could also commit this PR and create new release but I'd like at least an agreement before.