do not mix changesets

[davidzhao]

including private packages was causing changesets to fail

[changeset-bot]

⚠️ No Changeset found

Latest commit: b8f591b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 8 packages

Name	Type
livekit-server-sdk	Patch
@livekit/rtc-node	Patch
agent-dispatch	Patch
@livekit/rtc-node-darwin-arm64	Patch
@livekit/rtc-node-darwin-x64	Patch
@livekit/rtc-node-linux-arm64-gnu	Patch
@livekit/rtc-node-linux-x64-gnu	Patch
@livekit/rtc-node-win32-x64-msvc	Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[lukasIO]

From their docs, it appears that the "correct" way of handling packages that should not be published is to simply set private: true in package.json and not add them to the ignored packages in the changesets config, for reference

[davidzhao]

From their docs, it appears that the "correct" way of handling packages that should not be published is to simply set private: true in package.json and not add them to the ignored packages in the changesets config, for reference

that makes sense.. looks like all of the examples here have been set as "private": "true"... which might be why it's busted