- Skip the device-builder downstream job on beta/release target
branches. Those branches lag behind device-builder@main, so a
newer device-builder API requirement would falsely fail the run
without reflecting any problem in the PR itself. Mirrors the
same skip detect_memory_impact_config already does.
- Broaden the trigger to any non-C++ file under esphome/. The
package ships data files via include-package-data = true (e.g.
esphome/idf_component.yml, dashboard templates, JSON), so a
Python-only filter under-fires for changes that still affect
what device-builder installs.
Tests cover both: per-file behavior (with the skip mocked off) and
the beta/release skip itself short-circuiting before changed_files
is even consulted.
J. Nick Koston
520371c4a2