custom-components / breaking_changes

Component to show potential breaking_changes in the current published version based on your loaded components

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

At the time of archiving the integration has not worked in over a year.

Old readme

GitHub Release GitHub Activity License

Project Maintenance BuyMeCoffee

Discord Community Forum

Integration to show potential breaking_changes in the current published version based on your loaded components.

How it works.

hachanges uses web scraping on the blogpost for the release that it tries to show, and determine which breaking change to list. The webscraping is done in a Cloudflare worker and served as a JSON API at https://hachanges.entrypoint.xyz/v1/

This will list breaking changes on versions for versions released after the one you are running up to the latest stable version.

This will only list breaking changes in 2021.3 and newer.

Examples: You run version 2021.3.0, and 2021.6.0 is published, it will show breaking changes for 2021.4, 2021.5, 2021.6. You run version 2021.3.0, and 2021.3.0 is published, it will not show anything. You run version 2021.3.0, and 2021.4.0 is published, it will show breaking changes for 2021.4.

This component will set up the following platforms.

Platform Description
sensor Show info about potential issue with your configuration before upgrading.

Installation

  1. Install with HACS
  2. Add breaking_changes: to your HA configuration.

Example configuration.yaml

breaking_changes:

Configuration options

Key Type Required Default Description
name string False Potential breaking changes Custom name for the entities.
scan_interval int False 300 Seconds between updates.

Contributions are welcome!

If you want to contribute to this please read the Contribution guidelines


About

Component to show potential breaking_changes in the current published version based on your loaded components

License:MIT License


Languages

Language:Python 100.0%