[Radar] Add changelog for updated Workers AI popularity metric

[devandrepascoa]

Summary

Adds a Radar changelog entry announcing that Workers AI model and task popularity is now measured by the number of inferences instead of the number of unique accounts, and now reflects public inferences only. This warns users that the model/task distributions and historical trends shown on Radar (and via the /ai/inference/summary and /ai/inference/timeseries_groups API endpoints) may shift as a result.

File

• src/content/changelog/radar/2026-06-09-radar-workers-ai-inference-metric.mdx

Notes

• Frontmatter validated against src/schemas/changelog.ts.
• Formatting follows existing src/content/changelog/radar/ entries (prettier proseWrap: preserve).

[cloudflare-docs-bot]

Review

⏸️ Automatic reviews for this PR are paused.

This PR has already received 2 automatic reviews. To run another review, a codeowner can comment /review or /full-review.

Tip: Keep PRs in draft mode until they are ready for review — the bot skips draft PRs automatically.

---

💡 1 suggestion found in commit ec8fcdc.

Suggestions (1)

File	Issue
changelog/radar/2026-06-09-radar-workers-ai-inference-metric.mdx line 15	Bullet lists with fewer than three items — Bullet list contains only two API endpoint items Fix: Consider writing the two endpoints as prose instead of a list

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.

[github-actions]

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

Pattern	Owners
/src/assets/images/	@cloudflare/pm-changelogs, @cloudflare/product-owners
/src/content/changelog/	@cloudflare/pm-changelogs, @cloudflare/product-owners

[ask-bonk]

One minor wording suggestion. Otherwise the entry is clear, accurate, and follows the changelog format.

[ask-bonk]

Reviewed PR #31337. Here's the summary:

Verdict: One minor wording suggestion posted; otherwise LGTM.

What changed:

• Added a new Radar changelog entry (2026-06-09-radar-workers-ai-inference-metric.mdx) announcing that Workers AI model and task popularity in Cloudflare Radar is now measured by the number of inferences (instead of unique accounts) and reflects public inferences only.
• Warns users that distributions and historical trends may shift, and identifies the affected API endpoints.

Actions taken:

• Added the product:radar label to the PR.
• Posted an inline suggestion on line 18 to replace "Check out" with "Explore" to match the tone of existing Radar changelog entries.

Findings:

• Frontmatter is valid against the changelog schema.
• Links are correctly formatted with root-relative paths for internal docs and proper external URLs for Radar pages.
• No MDX syntax issues (no unescaped special characters).
• Content is accurate and clearly explains the metric change and its impact.

github run

[github-actions]

Preview URL: https://487d5714.preview.developers.cloudflare.com
Preview Branch URL: https://apascoa-radar-6819-workers-ai-inference-changelog.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/changelog/post/2026-06-09-radar-workers-ai-inference-metric/	https://apascoa-radar-6819-workers-ai-inference-changelog.preview.developers.cloudflare.com/changelog/post/2026-06-09-radar-workers-ai-inference-metric/

[devandrepascoa]

Note: the Post Build → Link validation CI step fails on a pre-existing broken link unrelated to this PR — /email-routing/ in src/content/docs/dns/faq.mdx:112 (that path is now a 301 redirect to /email-service/, and the links validator rejects redirect-only links).

This PR only adds a Radar changelog entry and does not touch dns/faq.mdx, so the failure is not caused by these changes. It should be fixed separately. The Deploy Preview job succeeds independently, so the changelog preview is unaffected.