Re-enable hdmi_cec component

[newAM]

Proposed change

This change re-enables the hdmi_cec component.
The component was removed in #37707 because it had a dependency on typing, which has since been resolved with the latest release of pyCEC, 0.4.14.

konikvranik/pyCEC@v0.4.13...v0.4.14

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)
• 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:

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

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[homeassistant]

Hi @newAM,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[KevinCathcart]

If you intend to help work on this integration going forward (since you are now a maintainer of the upstream library), please add yourself to the codeowners in manifest.json too. (Then run python3 -m script.hassfest to update the top level CODEOWNERS file).

Otherwise, this looks good, of course.

[newAM]

If you intend to help work on this integration going forward (since you are now a maintainer of the upstream library)

I am not sure if this is a long-term position, I only have PyPi access to the upstream right now (no repository access), I am clarifying with the owner of pyCEC.
I am happy to put my name down if my maintainer status of pyCEC becomes an ongoing role 👍

[newAM]

I have repository access now, I added myself as a codeowner.

P.S. Sorry if rebasing changes is discouraged, I did not find anything in the developer workflow about it. I know some places dislike them, and others require them.

[MartinHjelmare]

Please add a link to the changelog or github commit compare range for the version bump in the PR description.

[newAM]

Please add a link to the changelog or github commit compare range for the version bump in the PR description.

Done! It is just two small commits between 0.4.13 and 0.4.14.

Commits in 0.4.14 since 0.4.13:

• konikvranik/pyCEC@b528dfb
• konikvranik/pyCEC@f1cf4b6

[MartinHjelmare]

That's not really accurate. I've added the commit compare range to the description.

[MartinHjelmare]

Thanks!

[newAM]

That's not really accurate. I've added the commit compare range to the description.

Things got a bit out of order :/. I made the release on a branch before I realized that I did not have permissions to merge it back into maater. The branches then got merged (rebased?) out of order. I added the tags retroactively to preserve as much history as possible, but it is what it is.

For the future I added a changelog and have some repository access, so there will be improved accounting of changes.

[TheDK]

Thanks newAM for driving this! I guess it will be in 0.116 next week or so?

[newAM]

This is my first contribution to home assistant so I know as much as you do :)

It seems like releases are currently on a 3 week cycle[1] so probably next week or the week after? There will be a beta before then though.

[KevinCathcart]

Release is currently planned for the 7th of October. This made the cutoff so it should be included, unless some show stopping issue is discovered requiring it to be rolled back, which seems unlikely.