Bump adext to 0.4.3

[tichris0]

This updates the requirement for adext to 0.4.3 which adds functionality that paves the way for a follow-up PR that will make use of it.

changelog: ajschmidt8/adext@v0.4.2...v0.4.3

Proposed change

Bump up adext dependency for alarmdecoder from 0.4.2 to 0.4.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 #
• This PR is related to issue: AlarmDecoder entities have no unique ID's, despite not being YAML configurable, and these entities not associated with Integration #79599
• 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
• 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.

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.

[epenet]

Please add link to the changelog, or at minimum a diff between library versions is added to the PR description.

[epenet]

See above comment

[home-assistant]

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.

[tichris0]

Please add link to the changelog, or at minimum a diff between library versions is added to the PR description.

I don't see any changelog for this library and the detailed description already had the library version diff. The summary line only had the end version and was missing the previous version so I've added that in the title.

[epenet]

It is the link that is missing in the detailed description.
See an example in #117383

[frenck]

and the detailed description already had the library version diff.

Sorry, I don't see such a link.

Could you please update the PR description to contain at least one (or multiple) of the following:

• A link to the release notes of this package version, and all versions in between.
• A link to the changelog of this package.
• A link to a Git(Hub) diff/compare view from the current version to the bumped version.

This allows us to review upstream changes, which is needed to decide this change is working as intended and/or if we can include it in, for example, a patch release of Home Assistant.

Thanks already! 👍

../Frenck

[tichris0]

It is the link that is missing in the detailed description. See an example in #117383

Ahh perfect. That's super useful. I see thanks. I'll add that in.

[tichris0]

and the detailed description already had the library version diff.

Sorry, I don't see such a link.

Could you please update the PR description to contain at least one (or multiple) of the following:

* A link to the release notes of this package version, and all versions in between.

* A link to the changelog of this package.

* A link to a Git(Hub) diff/compare view from the current version to the bumped version.

This allows us to review upstream changes, which is needed to decide this change is working as intended and/or if we can include it in, for example, a patch release of Home Assistant.

Thanks already! 👍

../Frenck

Yes makes sense, I wasn't sure how to do it in Github, but the example above made it clear :)

Stale

[frenck]

Thanks, @tichris0 👍

../Frenck