Skip to content

Fix hassfest dependency rule violations in Home Assistant manifest - #11

Merged
valexi7 merged 2 commits into
mainfrom
copilot/fix-hassfest-job-failure
Oct 2, 2026
Merged

valexi7 merged 2 commits into
mainfrom
copilot/fix-hassfest-job-failure

Conversation

Copilot AI commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

hassfest failed because the integration manifest declared dependencies that conflict with Home Assistant policy: it listed a core-managed package (cryptography) and pinned tmodbus to an incompatible/exact version. This change aligns manifest requirements with HA’s dependency constraints.

  • Manifest dependency alignment

    • Removed cryptography>=42 from custom_components/huawei_emma_management/manifest.json (core dependency, should not be declared by custom integration).
    • Replaced tmodbus==0.4.1 with tmodbus>=0.6.2 to match HA compatibility requirements and avoid exact pinning of HA-managed deps.
  • Resulting manifest delta

    "requirements": [
      "huawei-solar==3.0.6",
      "tmodbus>=0.6.2"
    ]

Co-authored-by: valexi7 <44439515+valexi7@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix failing GitHub Actions job hassfest Fix hassfest dependency rule violations in Home Assistant manifest Oct 2, 2026
Copilot AI requested a review from valexi7 October 2, 2026 05:48
@valexi7
valexi7 marked this pull request as ready for review October 2, 2026 05:49
@valexi7
valexi7 merged commit 807bb63 into main Oct 2, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants