Skip to content

Release of 0.8.8 - #442

Open
sveinse wants to merge 3 commits into
custom-components:masterfrom
sveinse:release-0.8.8
Open

sveinse wants to merge 3 commits into
custom-components:masterfrom
sveinse:release-0.8.8

Conversation

@sveinse

@sveinse sveinse commented Oct 13, 2026

Copy link
Copy Markdown
Collaborator

This PR is the release of (the long overdue) v0.8.8

@rhammen @steinmn please review the changelog text which will be the release message. Since you can't see the diff log yet, below is the full list of changes that will be listed on the release page. There is quite a bit of changes here, so I would be grateful if you have any comments or suggestions to the release text. Thanks!

🌻 What's Changed

@sveinse sveinse added this to the v0.8.8 milestone Oct 13, 2026
@rhammen

rhammen commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Thanks! Suggested replacement for the highlights section:

This is a maintenance release fixing a lot of minor issues. Main highlights are:

  * Fixed the recorder warning about the charger's state attributes exceeding 16 KB (#382, #421, #436).
    Heads-up: these state attributes are targeted to be removed entirely in 0.9.0 (#388).
  * More robust against Zaptec API and connection problems (#359, #392, #400, #417, #433).
  * Session details now update within seconds when a charging session starts or ends (#434).
  * Added sensors showing who authorized a charging session (#431).
  * Added German and French translations.

Plus in the paragraph below it:

  • Mention the azure-servicebus bump to 7.15.0, since it's not in the generated list. (I tested 7.15.0 against a live stream: connect, reconnect after errors and shutdown all fine, no duplicate messages.)
  • "we have update" → "we have updated", "Code quality have been" → "Code quality has been".

@steinmn

steinmn commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Given https://github.com/custom-components/zaptec/actions/runs/39033100222/job/117397405725, this release also needs to be marked as a requirement for HA 2026.11+ (once #445 is included)

@sveinse

sveinse commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator Author

I merged #445, but it still fails CI. I think the cause is hassfest that's not yet updated its dependencies.

@sveinse

sveinse commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator Author

I think I'd also would like to start to inform about the future migration to https://github.com/ha-zaptec-community/ha-zaptec so that when we make the move, the information about it is already out there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Setting up Zaptec integration fails Review all validation models and make sure we don't require something we don't use.

3 participants