Link blog post for network::get_use_address() migration in 2025.11.0 changelog

[bdraco]

dev pr esphome/developers.esphome.io#78

Description:

Updates the 2025.11.0 changelog to reference the new blog post documenting the network::get_use_address() breaking change migration. The blog post provides comprehensive examples for external component authors including version compatibility patterns and real-world usage.

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.rst when creating new documents for new components or cookbook.

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	9547f4a
🔍 Latest deploy log	https://app.netlify.com/projects/esphome/deploys/691f7bf6dd62b900086588f2
😎 Deploy Preview	https://deploy-preview-5654--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.

[Copilot]

Pull Request Overview

Updates the 2025.11.0 changelog to link a blog post documenting the network::get_use_address() breaking change migration, improving the migration guidance.

• Adds a reference to the Network get_use_address() Optimization blog post
• Updates the use_address breaking change description with clearer migration instructions

[coderabbitai]

Walkthrough

The changelog for version 2025.11.0 was updated to include a migration blog post reference for network address optimization and to clarify documentation of the use_address change regarding .c_str() removal when calling get_use_address().

Changes

Cohort / File(s)	Summary
Changelog Updates content/changelog/2025.11.0.md	Added migration blog post reference for network address optimization under Network Components section; updated use_address change entry to clarify .c_str() removal instead of prior phrasing about type changes and external component updates

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: linking a blog post for network::get_use_address() migration in the 2025.11.0 changelog, which matches the changeset.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of updating the changelog to reference the migration blog post with details about content and compatibility patterns.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch get_use_address

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5411221 and ac28bc0.

📒 Files selected for processing (1)

• content/changelog/2025.11.0.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

• Do not generate or add any sequence diagrams

Files:

• content/changelog/2025.11.0.md

⏰ 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 (2)

content/changelog/2025.11.0.md (2)

490-491: Added migration blog post reference for network optimization.

The new blog post link provides clear guidance for external component developers on the breaking change. This is appropriately placed in the developer-facing breaking changes section.

The URL references a blog post at developers.esphome.io/blog/2025/11/20/network-use-address-optimization/. Please verify that this URL is correct and the blog post has been published as part of the related developers documentation PR #78.

---

494-494: Clarified migration guidance for use_address API change.

The updated text now explicitly states that developers should remove .c_str() calls when using get_use_address(), providing concrete migration steps. This pairs well with the blog post reference and makes the breaking change immediately actionable.

---

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.}