chore: bump package versions

[kixelated]

Problem

Published packages have unreleased behavior since #3879, including the @moq/watch import fix in #4217. The manifests still advertise the old versions.

Summary

Patch bumps only. Nothing here removes or renames a public signature. Pre-1.0 additive APIs stay on the patch.

• @moq/auth 0.2.1. Legacy put/get scopes read as the subtree patterns they meant.
• @moq/binary 0.2.1. Stream consumer behavior.
• @moq/hang 0.5.1. Rendition cap, timeline consumer, gesture unlock.
• @moq/json 0.4.1. Desync and MissingSnapshot, and a defaulted generic snapshot config.
• @moq/net 0.4.1. Hidden announcements, lite-07 stream counts, and tail handling. New exports, existing call shapes kept.
• @moq/publish 0.5.1. Audio capture waits for a running audio context. JitterClock and RenditionJitter added.
• @moq/signals 0.2.5. race added.
• @moq/watch 0.6.1. Built package keeps media-captions external (fix(watch): keep media-captions external so the package imports outside a browser #4217). Gesture unlock moved inside the decoder.
• @moq/boy 0.4.1 and @moq/room 0.2.1. Teardown uses effect.race.
• Python moq-rs 0.5.1, Swift 0.5.1, Kotlin dev.moq:moq 0.5.1. Optional websocket and track fields with defaults.

Left alone

• Rust crates. release-plz owns them (chore: release #4199).
• Go go/wrapper/VERSION stays 0.7. The new options and Flush are additive, and CI owns the Go patch.
• @moq/flate, @moq/loc, @moq/msf, @moq/pattern. Only repository metadata or a dependency range changed.
• doc/setup/upgrade.md. Those version numbers name the 0.5.0 train that section describes.

Not published and not tagged.

(Written by Grok 4.7)

[coderabbitai]

Warning

Review limit reached

Next included review available in 2 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f64ec3ab-43a1-4f0e-becd-6f6e136482fa

📥 Commits

Reviewing files that changed from the base of the PR and between cd379fe and cff0f90.

⛔ Files ignored due to path filters (2)

• bun.lock is excluded by !**/*.lock
• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (15)

• js/auth/package.json
• js/binary/package.json
• js/hang/package.json
• js/json/package.json
• js/moq-boy/package.json
• js/net/package.json
• js/publish/package.json
• js/room/package.json
• js/signals/package.json
• js/watch/package.json
• kt/README.md
• kt/gradle.properties
• py/moq-rs/pyproject.toml
• swift/README.md
• swift/VERSION

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-26T01:32:11.680357Z	cff0f90	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[kixelated]

MERGE

Patch-only version bumps so published manifests match behavior already on main since #3879 (including the @moq/watch import fix in #4217). Diff is limited to version fields and matching lock/README install lines across JS, Python, Swift, and Kotlin — no API surface changes in this PR.

Positive improvement? Yes. Consumers currently install versions that do not advertise the shipped behavior; bumping the sources of truth is the right fix before publish.

Worth the complexity? Yes. Complexity is near zero: coordinated patch bumps only, with Rust left to release-plz and Go left alone for stated compatibility reasons.

Different approach? Not needed. Waiting for a larger minor would leave packages mislabeled; a release-plz-style bot for these non-Rust packages would be a separate process change, not a reason to block this PR.

Looks ready to merge once CI is green. Publish/tag remain out of scope per the PR body.

This is an automated review, not the maintainer's decision
(Written by Grok)