Add CLI/SDK version note to telemetry overview#411
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This is a documentation-only change to a telemetry overview page, which does not require deploy monitoring. To monitor this PR anyway, reply with |
There was a problem hiding this comment.
Risk assessment: Very Low
This PR adds a single informational callout to browsers/telemetry/overview.mdx explaining that telemetry requires recent CLI/SDK versions. The diff is documentation-only, limited to one existing MDX page, with no production logic, config, infrastructure, or navigation changes. I found no CODEOWNERS file or existing approval blocking automation approval.
Sent by Cursor Automation: Assign PR reviewers


Summary
<Info>block to the telemetry overview noting that telemetry is a recent addition, with upgrade pointers for the CLI (kernel upgrade) and SDKs if the options/commands aren't yet available.Context
There was no note anywhere in the docs about minimum/required CLI or SDK versions for the telemetry feature. This is a discrete, generic upgrade hint (no hard version pin, consistent with the rest of the docs) placed on the feature's entry page.
Notes
Note
Low Risk
Documentation-only MDX change with no runtime, API, or security impact.
Overview
Adds an
<Info>callout on the telemetry overview page, right after the categories intro and before Enabling telemetry.It states that telemetry is new and tells readers to upgrade the CLI (
kernel upgrade) and SDKs (@onkernel/sdk, Pythonkernel) iftelemetryoptions ortelemetry streamare missing. There is no pinned minimum version—only a generic upgrade pointer.Reviewed by Cursor Bugbot for commit a19925b. Bugbot is set up for automated code reviews on this repo. Configure here.