Fix esp_hosted version specifier

[swoboda1337]

Description:

Use ==2.7.0 instead of ^2.7.0 to pin the exact esp_hosted version in the build instructions.

Related issue (if applicable): N/A

Pull request in esphome with YAML changes (if applicable):

N/A

Checklist:

• I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
  or

• I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

• Link added in /components/_index.md when creating new documents for new components or cookbook.

New Component Images

If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.

To generate a component image:

1. Comment on this pull request with the following command, replacing component_name with your component name in lower_case format with underscores (e.g., bme280, sht3x, dallas_temp):

   @esphomebot generate image component_name
   

2. The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.

3. Extract the SVG file and place it in the /static/images/ folder of this repository.

4. Use the image in your component's index table entry in /components/_index.md.

Example: For a component called "DHT22 Temperature Sensor", use:

@esphomebot generate image dht22

🤖 Generated with Claude Code

[coderabbitai]

Walkthrough

Documentation update pinning the ESP hosted dependency version from compatible specification (^2.7.0) to exact match (==2.7.0) in an example idf.py invocation within the component documentation.

Changes

Cohort / File(s)	Summary
Documentation content/components/update/esp32_hosted.md	Updated dependency version specifier from ^2.7.0 (compatible) to ==2.7.0 (exact match) in example code

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [esp32_hosted] Update ESP Hosted version to 2.7.0 #5752: Modifies the same ESP hosted example invocation with related version specification changes

Suggested labels

current

Suggested reviewers

• bdraco

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the esp_hosted version specifier from a compatible version constraint to an exact version pin.
Description check	✅ Passed	The description directly explains the change: switching from ^2.7.0 to ==2.7.0 to pin the exact esp_hosted version in build instructions, which matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a5920b8 and aa18caa.

📒 Files selected for processing (1)

• content/components/update/esp32_hosted.md

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

• Do not generate or add any sequence diagrams

Files:

• content/components/update/esp32_hosted.md

🧠 Learnings (1)

📓 Common learnings

Learnt from: jesserockz
Repo: esphome/esphome-docs PR: 4865
File: .github/workflows/needs-docs.yml:0-0
Timestamp: 2025-05-01T03:29:47.922Z
Learning: In the esphome-docs repository, the "current" label is automatically added by a bot to pull requests, making it a reliable indicator for the target branch.

Learnt from: CR
Repo: esphome/esphome-docs PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-08-24T00:13:13.459Z
Learning: Open pull requests against the correct base branch: use `current` for documentation-only revisions and `next` for changes tied to new features in esphome/esphome

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build

🔇 Additional comments (1)

content/components/update/esp32_hosted.md (1)

74-74: Pinning version improves build reproducibility.

The change from ^2.7.0 (compatible spec) to ==2.7.0 (exact version) aligns with the documented requirement in the line 67 comment and ensures users building from these instructions get the exact tested configuration. This is good practice for reproducible documentation examples.

---

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 and usage tips.}

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	ce1dd33
🔍 Latest deploy log	https://app.netlify.com/projects/esphome/deploys/69570741e25a300008e29ce5
😎 Deploy Preview	https://deploy-preview-5831--esphome.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[swoboda1337]

Thanks