docs(rtc-node): remove outdated Developer Preview notice from README - #718
Merged
Conversation
The README stated the SDK was "in Developer Preview mode and not ready for production use". That has not been accurate for some time: the package has shipped regular releases since 2024 (currently 0.13.x) and @livekit/agents declares @livekit/rtc-node as a peer dependency. Removes the notice block entirely to match the Python realtime SDK README, which has no such banner. The feedback/Slack line it contained is already covered by the "Getting help / Contributing" section at the bottom of this README. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 88eadcf The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
theomonnom
approved these changes
Sep 8, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
@livekit/rtc-nodeREADME still opens with:This came up from a customer (via support) who noticed the mismatch between that label and the package's actual status. They're right — it's stale:
@livekit/agentsv1.8.0 declares@livekit/rtc-node: ^0.13.34as a peer dependency, so anyone running the Node Agents SDK is already depending on it.Because this text renders on npmjs.com, it's the first thing evaluating customers read.
Change
Removes the notice block. This matches
livekit/python-sdks, whose realtime SDK README has no equivalent banner (and never did —git log -S "Developer Preview"on that repo is empty); it goes straight from the description into usage.The "we welcome feedback / #dev channel" line that lived in the same blockquote is dropped too, since the Getting help / Contributing section at the bottom of this README already says the same thing — again matching the Python repo's structure.
Deliberately not replacing it with a "production ready" claim. That reads as a support commitment and invites follow-up questions about documented scale limits, which is a product/DevRel call rather than a README change.
Includes a patch changeset so the corrected README gets republished to npm.
Note for reviewers
Node
@livekit/rtc-nodeis still0.13.xwhile Pythonlivekit-rtcis at1.1.17. I considered keeping a short "not yet 1.0, breaking changes may land in minor versions" caveat to reflect that, but opted for consistency with the Python README. Happy to add it back if you'd rather be explicit about the 0.x contract.🤖 Generated with Claude Code