Skip to content

Bump python-duco-client to 0.4.0#169776

Merged
zweckj merged 2 commits into
home-assistant:devfrom
ronaldvdmeer:feat/duco-bump-python-duco-client-0.4.0
May 5, 2026
Merged

Bump python-duco-client to 0.4.0#169776
zweckj merged 2 commits into
home-assistant:devfrom
ronaldvdmeer:feat/duco-bump-python-duco-client-0.4.0

Conversation

@ronaldvdmeer
Copy link
Copy Markdown
Contributor

@ronaldvdmeer ronaldvdmeer commented May 4, 2026

Proposed change

Bump the python-duco-client dependency from 0.3.10 to 0.4.0 for the duco integration.

The new version adds typed API metadata via an expanded ApiInfo model (public_api_version, reported_api_version) and extends BoardInfo with optional public_api_version and software_version fields. All new fields are parsed defensively so older and newer firmware variants remain compatible.

The diagnostics snapshot has been updated to include the two new BoardInfo fields.

Changelog: https://github.com/ronaldvdmeer/python-duco-client/blob/main/CHANGELOG.md
Diff link: ronaldvdmeer/python-duco-client@v0.3.10...v0.4.0

Diff summary (0.3.10 → 0.4.0):

  • ApiInfo: added public_api_version, reported_api_version, typed endpoint inventory
  • BoardInfo: added optional public_api_version, software_version

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue:
  • This PR is related to issue:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

Copilot AI review requested due to automatic review settings May 4, 2026 22:08
@home-assistant home-assistant Bot added cla-signed dependency Pull requests marked as a dependency upgrade has-tests integration: duco small-pr PRs with less than 30 lines. by-code-owner Quality Scale: platinum labels May 4, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Duco integration’s pinned python-duco-client dependency to v0.4.0 and aligns diagnostics snapshot expectations with the library’s expanded BoardInfo model.

Changes:

  • Bump python-duco-client from 0.3.10 to 0.4.0 for the Duco integration.
  • Regenerate/update Duco diagnostics snapshot to include the newly exposed BoardInfo fields (public_api_version, software_version).
  • Sync generated requirements files (requirements_all.txt, requirements_test_all.txt) with the new pin.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
tests/components/duco/snapshots/test_diagnostics.ambr Updates expected diagnostics output to include new BoardInfo fields (as None in the test fixture).
requirements_test_all.txt Updates the test requirements pin for python-duco-client to 0.4.0.
requirements_all.txt Updates the global generated requirements pin for python-duco-client to 0.4.0.
homeassistant/components/duco/manifest.json Updates the integration requirement pin to python-duco-client==0.4.0.

@ronaldvdmeer ronaldvdmeer marked this pull request as ready for review May 4, 2026 22:11
Copy link
Copy Markdown
Member

@joostlek joostlek left a comment

Choose a reason for hiding this comment

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

Please add link to the diff

@home-assistant home-assistant Bot marked this pull request as draft May 4, 2026 22:19
@home-assistant
Copy link
Copy Markdown
Contributor

home-assistant Bot commented May 4, 2026

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@ronaldvdmeer
Copy link
Copy Markdown
Contributor Author

ronaldvdmeer commented May 4, 2026

Please add link to the diff

Description updated

@ronaldvdmeer ronaldvdmeer marked this pull request as ready for review May 4, 2026 22:25
@home-assistant home-assistant Bot requested a review from joostlek May 4, 2026 22:25
@zweckj zweckj merged commit 74971eb into home-assistant:dev May 5, 2026
88 of 90 checks passed
rajlaud pushed a commit to rajlaud/home-assistant that referenced this pull request May 5, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators May 6, 2026
@frenck frenck added this to the 2026.5.1 milestone May 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants