Bump lupupy dependency to v0.2.3

[majuss]

Proposed change

majuss/lupupy@4dbd888...v0.2.3

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 Lupusec component returning error with __init__.py #82119
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• 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
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[majuss]

@MartinHjelmare could you please have a look at this? I don't really understand the output. The test which validates the config options failed?

[frenck]

@majuss The test failure is not related. I've restarted the failing job.

As for the version bump, can we please tag the version on the GitHub repository of the package source code? Preferably using the releases feature on GitHub.

That would give everybody a better insight into what changed between versions.

../Frenck

[majuss]

The pipeline failed again :/

I created a lupupy release.

[frenck]

Thanks, @majuss 👍