Bump jaraco.abode to 5.1.2

[jaraco]

• Bump the dependency on jaraco.abode.
• Replace constants with their literal values.

Closes #115561

See jaraco.abode history for changes between 3.3.0 and 5.1.2.

Breaking change

Proposed change

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 How to update to latest jaraco.abode #115561
• 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
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• (N/A) Tests have been added to verify that the new code works.

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

• (N/A) 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.

[home-assistant]

Hi @jaraco

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!

[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.

[home-assistant]

Hey there @shred86, mind taking a look at this pull request as it has been labeled with an integration (abode) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of abode can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign abode Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[jaraco]

That's interesting that ruff is failing. I made these changes using an editor with ruff configured for "format on save", so I'm surprised that didn't maintain the format expectation.

Oh, I see now, my editor wasn't formatting due to running an old version.

[jaraco]

Hmm. Ruff 0.3.7 is only a month old, so it's not really a bug in my editor that it hasn't downloaded the bleeding edge release. I'll just format manually.

[jaraco]

• The manifest file has all fields filled out correctly.

I'm leaving the codeowner unchanged for now. Maybe it makes sense to make me codeowner, but I'm not sure about that. I'd prefer for someone with homeassistant+abode to be the owner. That may be me some day, or I may accept that responsibility, but it seems out of the scope of this change.

Stale

[joostlek]

I mean, massive thanks for helping out :)

[joostlek]

If you could maybe take a look at the open issues (and maybe checkout some issues that got closed because they got stale) and maybe give an opinion on where the issue lies, that'd be awesome. If time allows me (because thesis deadline is getting close) I am happy to help out with the integration at the HA side.

If you use discord, feel free to send me a message, would love to stay in contact :)