Add changelog: legacy Tunnel routes and connections API endpoints retiring Oct 5, 2026#31879
Add changelog: legacy Tunnel routes and connections API endpoints retiring Oct 5, 2026#31879nikitacano wants to merge 3 commits into
Conversation
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
There was a problem hiding this comment.
Verdict: 2 style guide issues to address before merge.
Issues:
- MEDIUM (line 98): Heading uses contraction "we're" — style guide prohibits all contractions.
- LOW (line 11): Directional language "below" — style guide prohibits "above" / "below" in prose.
Posted 2 inline suggestions.
|
Review completed for PR #31879. Summary: This PR adds a changelog entry announcing two Cloudflare Tunnel / Mesh API deprecations effective October 5, 2026:
The entry includes migration steps, before/after Labels applied: Issues flagged (2 inline suggestions posted):
No build breakers or technical inaccuracies found. |
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsChecks PR title, description, and redirect checklist. No convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
b8e509e to
e5f35d1
Compare
|
CI run failed: build logs |
Broken LinksFound 4 broken link(s) across 3 file(s).
|
…iring Oct 5, 2026
Announces two related API changes taking effect October 5, 2026:
- CIDR-encoded route create/update/delete endpoints
(POST|PATCH|DELETE /accounts/{account_id}/teamnet/routes/network/{ip_network_encoded})
are removed in favor of the existing route_id-based endpoints.
- The connections field is removed from Cloudflare Tunnel (cfd_tunnel) and
Cloudflare Mesh (warp_connector) list/get responses; callers should use the
dedicated .../connections endpoints instead.
Includes migration steps, before/after curl examples, cloudflared and
Terraform (cloudflare_zero_trust_tunnel_route) guidance, and links to the
relevant API reference pages.
Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>
e5f35d1 to
8e1a58b
Compare
Summary
Adds a Cloudflare Tunnel changelog entry announcing two related API deprecations, both effective October 5, 2026:
POST/PATCH/DELETE /accounts/{account_id}/teamnet/routes/network/{ip_network_encoded}) are removed in favor of the existingroute_id-based endpoints (POST /accounts/{account_id}/teamnet/routes,PATCH/DELETE /accounts/{account_id}/teamnet/routes/{route_id}).connectionsfield removed from list/get responses. Cloudflare Tunnel (cfd_tunnel) and Cloudflare Mesh (warp_connector) list and get endpoints no longer return theconnectionsarray. Callers should use the dedicated.../connectionsendpoints instead.The entry includes a before/after comparison table, migration steps,
curlexamples, guidance forcloudflaredand thecloudflare_zero_trust_tunnel_routeTerraform resource, and links to the relevant API reference pages. Endpoint paths, method pages, and Terraform resource names were verified directly against the live API reference before writing.Documentation checklist