Skip to content

fix: update RealtimeKit SDK api reference#32126

Open
agents-git-bot[bot] wants to merge 1 commit into
productionfrom
update-realtimekit-api-reference-20260717-043742
Open

fix: update RealtimeKit SDK api reference#32126
agents-git-bot[bot] wants to merge 1 commit into
productionfrom
update-realtimekit-api-reference-20260717-043742

Conversation

@agents-git-bot

Copy link
Copy Markdown
Contributor

🤖 Automated Documentation Update

@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 6 warnings found in commit fa2a65d.

Fix in your agent
Fix the following review findings in PR #32126 (https://github.com/cloudflare/cloudflare-docs/pull/32126).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, fix all legitimate findings. For any you decide to skip,
post a comment on this PR with the finding ID and your reasoning.

---

## Code Review

### Warnings (6)

#### CR-adcf8709d538 · Misleading code example variable
- **File:** `src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipant.md` line 18
- **Issue:** `participant4` is assigned the result of `meeting.participants.active.toArray().filter(...)`, which returns an array of participants. The previous variables (`participant1`, `participant2`, `participant3`) hold single `RTKParticipant` objects, so the singular name implies the wrong type.
- **Fix:** Rename the variable to something plural like `participantsNamedJohn`, or if a single participant is intended, index into the filtered array (e.g. `[0]`).

#### CR-d7bc6d200a55 · Staging version in public API reference
- **File:** `src/content/docs/realtime/realtimekit/core/api-reference/RTKLivestream.md` line 4
- **Issue:** The added `web_core_version: 2.0.1-staging.2` uses a staging/pre-release version. Every other RealtimeKit core API reference page uses the stable `web_core_version: 1.2.4`, creating an unexplained inconsistency in the public docs.
- **Fix:** Verify the version is intentional and stable. If the SDK is moving to 2.0.1, update every API reference page consistently; if only this module changed, use the released version rather than a staging tag.

#### CR-d6dd287a3261 · Inconsistent SDK version across generated API reference
- **File:** `src/content/docs/realtime/realtimekit/core/api-reference/RTKParticipantMap.md` line 4
- **Issue:** This file was updated to `web_core_version: 2.0.1-staging.2`, but every other generated API reference page in `src/content/docs/realtime/realtimekit/core/api-reference/` remains at `web_core_version: 1.2.4`. A staging pre-release version is also unusual for published public API docs.
- **Fix:** Verify whether this single-file upgrade to a staging version is intentional. If updating the SDK version, apply it consistently to all generated files in the same directory and prefer a stable release over a `-staging` pre-release in public docs.

#### CR-7d7df1bfc7f9 · Inconsistent staging SDK version
- **File:** `src/content/docs/realtime/realtimekit/core/api-reference/RTKPip.md` line 4
- **Issue:** The added `web_core_version: 2.0.1-staging.2` uses a pre-release/staging SDK version, while every other file in `src/content/docs/realtime/realtimekit/core/api-reference/` uses the stable release version `1.2.4`. Publishing API reference metadata tied to a staging build on the production branch is inconsistent and may surface unreleased/changing APIs to users.
- **Fix:** Regenerate this page against the released RealtimeKit SDK version used by the rest of the core API reference (currently `1.2.4`), or verify that publishing a staging-version API reference is intentional.

#### CR-ef0353c39f29 · Inconsistent API reference version
- **File:** `src/content/docs/realtime/realtimekit/core/api-reference/RTKPlugins.md` line 4
- **Issue:** This file updates web_core_version to 2.0.1-staging.2, but the other 19 files in src/content/docs/realtime/realtimekit/core/api-reference/ still have web_core_version: 1.2.4.
- **Fix:** If the whole RealtimeKit SDK API reference was regenerated, update all sibling files to the same version. If only RTKPlugins changed in this release, document that intent explicitly.

#### CR-eda0c68ec41b · Inconsistent SDK version in auto-generated API reference
- **File:** `src/content/docs/realtime/realtimekit/core/api-reference/RTKSelfMedia.md` line 4
- **Issue:** `web_core_version` is changed to `2.0.1-staging.2` here, but every other RealtimeKit API reference page in the same directory still uses `1.2.4`.
- **Fix:** Regenerate all RealtimeKit API reference pages from the same SDK version so the version metadata is consistent across the section, and use a stable release version rather than a `-staging` prerelease tag in production docs.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (6)
File Issue
realtime/realtimekit/core/api-reference/RTKParticipant.md line 18 Misleading code example variableparticipant4 is assigned the result of meeting.participants.active.toArray().filter(...), which returns an array of participants. The previous variables (participant1, participant2, participant3) hold single RTKParticipant objects, so the singular name implies the wrong type. Fix: Rename the variable to something plural like participantsNamedJohn, or if a single participant is intended, index into the filtered array (e.g. [0]).
realtime/realtimekit/core/api-reference/RTKLivestream.md line 4 Staging version in public API reference — The added web_core_version: 2.0.1-staging.2 uses a staging/pre-release version. Every other RealtimeKit core API reference page uses the stable web_core_version: 1.2.4, creating an unexplained inconsistency in the public docs. Fix: Verify the version is intentional and stable. If the SDK is moving to 2.0.1, update every API reference page consistently; if only this module changed, use the released version rather than a staging tag.
realtime/realtimekit/core/api-reference/RTKParticipantMap.md line 4 Inconsistent SDK version across generated API reference — This file was updated to web_core_version: 2.0.1-staging.2, but every other generated API reference page in src/content/docs/realtime/realtimekit/core/api-reference/ remains at web_core_version: 1.2.4. A staging pre-release version is also unusual for published public API docs. Fix: Verify whether this single-file upgrade to a staging version is intentional. If updating the SDK version, apply it consistently to all generated files in the same directory and prefer a stable release over a -staging pre-release in public docs.
realtime/realtimekit/core/api-reference/RTKPip.md line 4 Inconsistent staging SDK version — The added web_core_version: 2.0.1-staging.2 uses a pre-release/staging SDK version, while every other file in src/content/docs/realtime/realtimekit/core/api-reference/ uses the stable release version 1.2.4. Publishing API reference metadata tied to a staging build on the production branch is inconsistent and may surface unreleased/changing APIs to users. Fix: Regenerate this page against the released RealtimeKit SDK version used by the rest of the core API reference (currently 1.2.4), or verify that publishing a staging-version API reference is intentional.
realtime/realtimekit/core/api-reference/RTKPlugins.md line 4 Inconsistent API reference version — This file updates web_core_version to 2.0.1-staging.2, but the other 19 files in src/content/docs/realtime/realtimekit/core/api-reference/ still have web_core_version: 1.2.4. Fix: If the whole RealtimeKit SDK API reference was regenerated, update all sibling files to the same version. If only RTKPlugins changed in this release, document that intent explicitly.
realtime/realtimekit/core/api-reference/RTKSelfMedia.md line 4 Inconsistent SDK version in auto-generated API referenceweb_core_version is changed to 2.0.1-staging.2 here, but every other RealtimeKit API reference page in the same directory still uses 1.2.4. Fix: Regenerate all RealtimeKit API reference pages from the same SDK version so the version metadata is consistent across the section, and use a stable release version rather than a -staging prerelease tag in production docs.

Conventions

No convention issues found.

Style Guide Review

No style-guide issues found.

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.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.

@github-actions

Copy link
Copy Markdown
Contributor

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

Pattern Owners
/src/content/docs/realtime/ @cloudflare/product-owners, @cloudflare/realtime, @cloudflare/RealtimeKit, @roerohan, @ravindra-cloudflare

@ravindra-cloudflare

Copy link
Copy Markdown
Contributor

Looking into it

@github-actions

Copy link
Copy Markdown
Contributor

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.

2 participants