Rename esp32_improv to improv_ble

[bharvey88]

Version: 26.9.17.2

What does this implement/fix?

esphome/esphome#19264 renamed the esp32_improv component to improv_ble and decoupled it from the ESP32 platform. The old top-level key still resolves through an alias, but every build now logs:

WARNING The 'esp32_improv:' top-level key is deprecated; rename it to 'improv_ble:'. Removed in 2027.4.0.

This renames the key and its id. I checked what else changed in #19264, since the title also says "decouple from ESP32":

• Every YAML option is unchanged: id, authorizer, status_indicator, identify_duration, authorized_duration, wifi_timeout, next_url and the on_provisioned / on_provisioning / on_start / on_state / on_stop triggers, with the same defaults.
• What changed is internal: the C++ namespace, the component and trigger class names, the USE_* defines, the log tag, and the dump_config heading. None of that is reachable from this config, which has no lambdas touching the component.
• The decoupling replaces DEPENDENCIES = ["wifi", "esp32"] with a backend table plus cv.only_on(["esp32"]). ESP32 is still the only BLE server backend, so behaviour on the CAST-1 is identical.
• improv_serial: is unaffected. Its key, options and schema are unchanged.

min_version and CI

improv_ble is in no release tag yet. The latest release is 2026.9.0 and the rename ships in 2026.10.0, so min_version goes from 2026.8.0 to 2026.10.0.

This PR will sit with failing CI until 2026.10.0 is released. ci.yml runs the stable and beta legs only, and both are on versions older than 2026.10.0, so both fail the min_version check. The beta leg will go green as soon as 2026.10.0b1 is published, the stable leg once 2026.10.0 lands. Same pattern as AIR-1 #124. Validated locally against an ESPHome dev checkout: INFO Configuration is valid! with no deprecation warning.

The min_version bump is not a breaking change for users. It only affects people compiling this YAML themselves; precompiled and OTA users are unaffected.

Types of changes

• Bugfix (fixed change that fixes an issue)
• New feature (thanks!)
• Breaking change (repair/feature that breaks existing functionality)
• Dependency Update - Does not publish
• Other - Does not publish
• Website of github readme file update - Does not publish
• Github workflows - Does not publish

Checklist / Checklijst:

• The code change has been tested and works locally
• The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

• Added/updated documentation for the web page

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 55ef5664-6fb3-43a9-81f3-138b59f6f827

📥 Commits

Reviewing files that changed from the base of the PR and between 0b34fb2 and 1bb2363.

📒 Files selected for processing (1)

• Integrations/ESPHome/Core.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}