Skip to content

v2.2.0

Choose a tag to compare

View all tags
@eXPerience83 eXPerience83 released this 19 May 07:37
v2.2.0
26bc35c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

2.2.0

Stable release for the 2.2.0 cycle.

This release focuses on reliability, safer error handling, stale-data protection, forecast extraction cleanup, validation consistency, CI alignment, and documentation polish.

Added

  • Added stale-data expiration for malformed Google Pollen API payloads: cached coordinator data is now reused only while it remains within the effective TTL.
  • Added repository guidance for future agent reviews to avoid overengineering defensive parsing and tests for highly unlikely upstream payload shapes.

Changed

  • Hardened HTTP and config-flow error redaction so API keys and precise coordinates are redacted from client and validation error messages.
  • Centralized latitude and longitude validation across config flow and runtime setup.
  • Centralized forecast sensor mode and forecast-days compatibility validation across setup and options flow.
  • Cached daily summary sensor payloads per coordinator data object to avoid redundant daily_summary(...) recomputation for the same sensor update.
  • Refactored coordinator forecast extraction to reuse shared private helpers for API date extraction, forecast entry construction, and forecast list construction.
  • Aligned package, release, and regular test validation by compiling Python sources and running Ruff, Black, and pytest before release packaging.
  • Audited and streamlined the test suite while preserving coverage for redaction, validation helpers, stale-data TTL behavior, forecast extraction, config flow validation, and Home Assistant setup flows.
  • Polished documentation around API key sharing, Google Maps Platform pricing/quota verification, quota-cap latency, and Markdown callout formatting.

Fixed

  • Prevented indefinitely stale pollen data from remaining available when the API repeatedly returns missing or invalid dailyInfo after a previous successful refresh.
  • Prevented malformed forecast date payloads from interrupting otherwise usable coordinator updates.
  • Preserved D+1/D+2 type sensor shaping when forecast days contain missing indexes, malformed dates, or malformed forecast index payloads.
  • Ensured config-flow error placeholders use safe fallback messages when upstream exception messages are empty.
  • Prevented precise invalid stored coordinates from being logged during runtime setup failures.

Validation

  • Lint: success.
  • Tests: success, 283 passed.
  • Validate with hassfest: success.
  • Validate with HACS: success.
  • Release workflow validates the ZIP structure before uploading pollenlevels.zip.

Notes

  • No entity IDs, unique IDs, translation keys, public sensor keys, Home Assistant minimum version, or Python requirement were changed in this final release.
  • This release includes the changes previously tested through the 2.2.0 alpha and beta pre-releases.

What's Changed

Full Changelog: v2.1.1...v2.2.0

Contributors

eXPerience83
Assets 3
Loading