Release 1.1.0

[dewet22]

Summary

Version bump to 1.1.0 collecting the following changes since v1.0.2:

• feat (feat: persist PlantCapabilities across restarts (#48) #62): Persist PlantCapabilities across restarts — warm-start detection, advisory Repairs issue + reload on topology change, redetect_plant service (Persist PlantCapabilities across restarts to skip re-detection #48)
• feat (feat: expose_recommended_entities service + voice/LLM docs (#65) #66): expose_recommended_entities service — one-shot voice/LLM assistant exposure for 17 headline entities; voice assistant docs (Document Assist/LLM exposure for energy entities; consider opt-in auto-expose #65)
• docs (Migrate long-term energy stats from GivTCP #67): GivTCP → givenergy_local migration guide and helper script
• docs: Passive mode reframing; parallel-running and GivTCP coexistence notes
• build (build: bump requires-python floor to 3.14.2 #61): Bump requires-python floor to >=3.14.2
• chore (chore: retire v1.0, bump givenergy-modbus to 2.0.4 #59): Retire v1.0 branch; bump givenergy-modbus floor to 2.0.4
• chore (chore(ci): validate bumper version input before downstream use #60): Version-format validation in auto-bumper workflow
• chore: Cap givenergy-modbus at <2.1 — 2.1 is expected to include breaking API changes (command dispatch refactor); compatibility will be a separate minor release

Test plan

• CI passes on this branch
• HACS validation passes
• Merge → tag v1.1.0 → release

🤖 Generated with Claude Code

Summary by CodeRabbit

• Updates
  • Integration version updated to 1.1.0
  • Dependency constraints refined for improved stability and compatibility

[coderabbitai]

Warning

Review limit reached

@dewet22, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 minutes and 50 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6946e3db-9f6d-4e5b-93a2-0372fc3112b8

📥 Commits

Reviewing files that changed from the base of the PR and between c13bc33 and c5fc01e.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml

📝 Walkthrough

Walkthrough

This PR updates the Home Assistant integration manifest to tighten the givenergy-modbus dependency constraint from <3.0.0 to <2.1 and bumps the integration version from 1.0.2 to 1.1.0.

Changes

Manifest Dependency and Version Update

Layer / File(s)	Summary
Givenergy-modbus dependency constraint and integration version custom_components/givenergy_local/manifest.json	The givenergy-modbus requirement upper bound is tightened from <3.0.0 to <2.1, and the integration version is bumped from 1.0.2 to 1.1.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• dewet22/givenergy-hass#57: Both PRs modify the givenergy-modbus version constraints and bump the integration version in the manifest.
• dewet22/givenergy-hass#59: Both PRs adjust the givenergy-modbus dependency constraint in the manifest.
• dewet22/givenergy-hass#53: Both PRs update the manifest, though #53 only bumps the integration version while this PR also tightens the dependency constraint.

Poem

🐰 A manifest tweaked with care so fine,
Tightening bounds and version's line,
Dependencies kissed by modbus's might,
From three to two-point-one shines bright! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Release 1.1.0' directly and clearly summarizes the main change: bumping the project version from 1.0.2 to 1.1.0 as documented in the manifest.json update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.1.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the manifest.json for the GivEnergy Local integration. It restricts the givenergy-modbus dependency version requirement to <2.1 (previously <3.0.0) and bumps the integration version from 1.0.2 to 1.1.0. There are no review comments, and I have no additional feedback to provide.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@custom_components/givenergy_local/manifest.json`:
- Line 12: The dependency upper bound for givenergy-modbus is inconsistent:
manifest.json pins "givenergy-modbus>=2.0.4,<2.1" while pyproject.toml allows
"<3.0.0"; make them consistent by updating pyproject.toml to use the same upper
bound "<2.1" (or alternatively change manifest.json to match if that is
intended) and regenerate the lockfile/CI dependencies so tests run against the
same range; ensure you update the givenergy-modbus spec in pyproject.toml (and
any poetry/lockfile) to match the manifest.json entry.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a3b2ae3b-4a89-4140-8a64-7d73c7c4deac

📥 Commits

Reviewing files that changed from the base of the PR and between 0075f01 and c13bc33.

📒 Files selected for processing (1)

• custom_components/givenergy_local/manifest.json

[dewet22]

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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	mypy@​2.0.0
	pytest@​9.0.3
	pytest-homeassistant-custom-component@​0.13.330
	ruff@​0.15.12
	pytest-asyncio@​1.3.0
	givenergy-modbus@​2.0.4

View full report