Skip to content

Conversation

@richardpolzer
Copy link
Contributor

Proposed change

Bump ekey-bionyxpy to 1.0.1

Changelog: https://github.com/richardpolzer/ekey-bionyx-api/releases/tag/1.0.1

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 link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

Copy link
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

This PR bumps the ekey-bionyxpy library dependency from version 1.0.0 to 1.0.1. This is a minor patch version update for the ekey Bionyx integration, which provides Home Assistant support for ekey biometric access control systems.

Key Changes

  • Updated dependency version from 1.0.0 to 1.0.1 across all requirement files

Reviewed changes

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

File Description
homeassistant/components/ekeybionyx/manifest.json Updated the requirements field to specify ekey-bionyxpy version 1.0.1
requirements_all.txt Updated ekey-bionyxpy dependency to version 1.0.1
requirements_test_all.txt Updated ekey-bionyxpy test dependency to version 1.0.1

Based on my review of this PR, I found no issues. This is a clean dependency version bump that:

✅ Updates all three required files consistently
✅ Maintains proper version pinning format (using ==)
✅ Is appropriate for a patch version update (1.0.0 → 1.0.1)
✅ Follows Home Assistant's dependency management practices

The changes are minimal and focused, which is expected for a patch version dependency update. No code changes are required since patch versions typically contain bug fixes and minor improvements that maintain backward compatibility.

Copy link
Member

@edenhaus edenhaus left a comment

Choose a reason for hiding this comment

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

Thanks @richardpolzer 👍

@edenhaus edenhaus added this to the 2025.12.4 milestone Dec 16, 2025
@edenhaus edenhaus merged commit a0a444e into home-assistant:dev Dec 16, 2025
73 checks passed
@richardpolzer richardpolzer deleted the ekey_bump_1.0.1 branch December 16, 2025 13:31
heindrichpaul pushed a commit to heindrichpaul/core that referenced this pull request Dec 17, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Dec 17, 2025
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.

3 participants