Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions custom_components/givenergy_local/manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
"iot_class": "local_polling",
"issue_tracker": "https://github.com/dewet22/givenergy-hass/issues",
"requirements": [
"givenergy-modbus>=2.0.4,<3.0.0"
"givenergy-modbus>=2.0.4,<2.1"
Comment thread
coderabbitai[bot] marked this conversation as resolved.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I found one alignment issue with the dependency cap: this release caps givenergy-modbus at <2.1 in the runtime manifest, but pyproject.toml still declares givenergy-modbus>=2.0.4,<3.0.0, and uv.lock still records that same project requirement.

That means HA/HACS users are protected from a future 2.1 install, but the dev/test environment can still resolve 2.1 later. I would mirror the <2.1 cap in pyproject.toml and refresh uv.lock, so CI, local tests, Dependabot/uv updates, and runtime installs all exercise the same compatibility boundary.

],
"version": "1.0.2"
"version": "1.1.0"
}
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ version = "0.0.0"
description = "Home Assistant custom component for GivEnergy inverters via local Modbus TCP"
requires-python = ">=3.14.2"
dependencies = [
"givenergy-modbus>=2.0.4,<3.0.0",
"givenergy-modbus>=2.0.4,<2.1",
]

[dependency-groups]
Expand Down
2 changes: 1 addition & 1 deletion uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading