Skip to content

Be robust in how we handle geocoding requests to Nominatim. #47

Be robust in how we handle geocoding requests to Nominatim.

Be robust in how we handle geocoding requests to Nominatim. #47

Triggered via push August 23, 2024 13:41
Status Success
Total duration 1m 16s
Artifacts
hassfest action
1m 7s
hassfest action
HACS Action
21s
HACS Action
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
hassfest action
[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.
hassfest action
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
hassfest action
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/