Skip to content

Bump pyOverkiz to 1.20.4#171626

Merged
zweckj merged 1 commit into
home-assistant:devfrom
iMicknl:bump-pyoverkiz-1.20.4
May 21, 2026
Merged

Bump pyOverkiz to 1.20.4#171626
zweckj merged 1 commit into
home-assistant:devfrom
iMicknl:bump-pyoverkiz-1.20.4

Conversation

@iMicknl
Copy link
Copy Markdown
Member

@iMicknl iMicknl commented May 20, 2026

Proposed change

https://github.com/iMicknl/python-overkiz-api/releases/tag/v1.20.4
https://github.com/iMicknl/python-overkiz-api/compare/v1.20.3..v1.20.4

Mainly dependency updates and additional enums.

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: fixes #
  • 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 20, 2026 19:56
@home-assistant home-assistant Bot added cla-signed dependency Pull requests marked as a dependency upgrade integration: overkiz small-pr PRs with less than 30 lines. Top 200 Integration is ranked within the top 200 by usage by-code-owner Quality Scale: No score labels May 20, 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 Overkiz integration dependency pin to pyoverkiz==1.20.4 to pick up the upstream patch release (dependency updates / additional enums per release notes).

Changes:

  • Bump pyoverkiz from 1.20.3 to 1.20.4 in the Overkiz integration manifest.
  • Synchronize the pinned version in requirements_all.txt and requirements_test_all.txt.

Reviewed changes

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

File Description
requirements_test_all.txt Updates the test requirements pin for pyoverkiz to 1.20.4.
requirements_all.txt Updates the global requirements pin for pyoverkiz to 1.20.4.
homeassistant/components/overkiz/manifest.json Updates the integration’s runtime requirement pin for pyoverkiz to 1.20.4.

@github-actions
Copy link
Copy Markdown

Check requirements

⚠️ Some checks require attention — see the details below.

Package Old New Repo Public CI Upload Release Pipeline PR Link Async Safe
pyoverkiz 1.20.3 1.20.4 ⚠️
📦 pyoverkiz: 1.20.3 → 1.20.4
  • Repo Public: ✅ https://github.com/iMicknl/python-overkiz-api is publicly accessible.
  • CI Upload: ⚠️ No PEP 740 provenance attestation present on PyPI. Upload method cannot be verified from PyPI alone.
  • Release Pipeline: ✅ Triggered by release: published, uses id-token: write OIDC with environment: release, and publishes via uv publish (trusted publisher). No static token or manual upload bypass. See release.yml.
  • PR Link: ✅ PR description links to the compare URL https://github.com/iMicknl/python-overkiz-api/compare/v1.20.3..v1.20.4 covering both versions.
  • Async Safe: ✅ No new blocking calls introduced in 1.20.3 → 1.20.4. The diff contains only StrEnum additions (OverkizCommand, Protocol, UIClass, UIWidget), a version bump in pyproject.toml, and uv.lock dependency updates — no async code paths were modified.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Check requirements (AW) · ● 2.3M ·

Copy link
Copy Markdown
Member

@TheJulianJES TheJulianJES left a comment

Choose a reason for hiding this comment

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

Lib changes look good. PR only needs to be rebased now, as the requirements_test_all.txt file no longer exists.

@iMicknl iMicknl force-pushed the bump-pyoverkiz-1.20.4 branch from eac333a to af033b6 Compare May 21, 2026 06:22
@zweckj zweckj merged commit 94c3ad2 into home-assistant:dev May 21, 2026
48 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators May 22, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

by-code-owner cla-signed dependency Pull requests marked as a dependency upgrade integration: overkiz Quality Scale: No score small-pr PRs with less than 30 lines. Top 200 Integration is ranked within the top 200 by usage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants