UL Transport 2.0.2
Maintenance release. Nothing about the integration's behaviour changed — 2.0.1 users gain the packaging and repository fixes below.
Fixed
manifest.jsonkey order. 2.0.1 shipped withafter_dependenciesin the wrong place, whichhassfestrejects (keys must be domain, name, then alphabetical).gtfs-realtime-bindingsraised to>=2.2.0from>=1.0.0. 1.0.0 declares no dependencies at all, so it could be installed without theprotobufthe live map's realtime feeds need. 2.2.0 declares it and leaves the version unpinned, so nothing else in Home Assistant is disturbed — and it is the version CI actually tests, which the old floor did not describe.
Added
- Brand assets under
custom_components/ul_transport/brand/, so HACS shows an icon rather than falling back to the core-only brands repository. - A
LICENSEfile. The README andpyproject.tomlalready said MIT; now the repository does too.
Changed
Repository housekeeping with no effect on the installed integration: CI actions pinned to commit SHAs and updated to current majors, Dependabot configured to keep them moving, ruff format applied and enforced in CI, and the test suite given the home-assistant-frontend wheel it needs to run outside a full Home Assistant install.
Upgrading from 2.0.1 is a straight HACS update — no configuration changes, and every entity keeps its id, history and name. If you are coming from 2.0.0, read the 2.0.1 notes as well: that release fixed the double reload on saving options, the per-request HTTP sessions, and the mangled rate-limit error.
Full changelog: 2.0.1...2.0.2