Skip to content

[Draft] Update ZT SNI for new client versions#31236

Open
lpraneis wants to merge 2 commits into
productionfrom
lpraneis/new-zt-sni
Open

[Draft] Update ZT SNI for new client versions#31236
lpraneis wants to merge 2 commits into
productionfrom
lpraneis/new-zt-sni

Conversation

@lpraneis
Copy link
Copy Markdown
Collaborator

@lpraneis lpraneis commented Jun 4, 2026

Summary

Update SNI for the new client versions.

Replaces #31144

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@lpraneis lpraneis requested review from a team, cf-rhett, csujedihy, elithrar and jiulingz as code owners June 4, 2026 15:41
@cloudflare-docs-bot
Copy link
Copy Markdown
Contributor

cloudflare-docs-bot Bot commented Jun 4, 2026

Review

❌ Review failed for commit 31cb648. This is usually a transient error — it will retry on the next push.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

This PR requires additional review attention because it affects the following areas:

Partials

This PR updates partial files, which are pieces of content used across multiple files in our Render component.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 4, 2026

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/cloudflare-one/team-and-resources/devices/ @ranbel, @cf-rhett, @csujedihy, @lpraneis, @jiulingz, @cloudflare/cf1-reviewers, @elithrar, @cloudflare/product-owners
/src/content/partials/cloudflare-one/warp/ @ranbel, @cf-rhett, @csujedihy, @lpraneis, @jiulingz, @cloudflare/cf1-reviewers, @elithrar, @cloudflare/product-owners

@ask-bonk ask-bonk Bot added the documentation Documentation edits label Jun 4, 2026
Copy link
Copy Markdown
Contributor

@ask-bonk ask-bonk Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR correctly updates the SNI documentation for new Cloudflare One Client versions. Two items need attention before merge.

  • MEDIUM — Add a changelog entry for this functional change. Customers need to know that client version 2026.6.0+ switches to api.devices.cloudflare.com so they can update firewall rules accordingly.
  • LOW — Remove [Draft] from the PR title and mark the PR as ready for review when appropriate. Also complete the documentation checklist in the PR description.

@ask-bonk
Copy link
Copy Markdown
Contributor

ask-bonk Bot commented Jun 4, 2026

Done. Here's a summary of the review for PR #31236:

What it changes:
Updates the documented SNIs (Server Name Indications) for the Cloudflare One Client. Starting with client version 2026.6.0, the client uses api.devices.cloudflare.com instead of the previous zero-trust-client.cloudflareclient.com and notifications.cloudflareclient.com. The change is applied in two places:

  1. The reusable partial cloudflare-one/warp/client-orchestration-ips
  2. The firewall reference page that renders that partial

Labels applied: documentation

Issues flagged:

  • MEDIUM: No changelog entry. Since this is a functional behavior change that affects firewall rules, customers should be notified so they can update allowlists when upgrading client versions.
  • LOW: PR is still in Draft state with [Draft] in the title. The author should remove [Draft] and mark it ready for review when appropriate, and complete the documentation checklist.

No inline code suggestions were needed — the MDX syntax is valid and the content is technically coherent.

github run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants