chore: release

[moq-bot]

🤖 New release

• moq-json: 0.4.0 -> 0.4.1 (✓ API compatible changes)
• moq-tokio: 0.19.11 -> 0.19.12 (✓ API compatible changes)
• moq-video: 0.0.26 -> 0.0.27 (✓ API compatible changes)
• moq-uring: 0.0.1 -> 0.0.2 (✓ API compatible changes)
• moq-boy: 0.5.0 -> 0.5.1
• moq-relay: 0.15.0 -> 0.15.1 (✓ API compatible changes)
• moq-transcode: 0.0.20 -> 0.0.21 (✓ API compatible changes)
• moq-cli: 0.12.0 -> 0.12.1
• moq-ffi: 0.4.0 -> 0.4.1
• hang: 0.21.0 -> 0.21.1
• moq-mux: 0.10.0 -> 0.10.1
• moq-audio: 0.0.26 -> 0.0.27
• libmoq: 0.6.0 -> 0.6.1
• moq-hls: 0.5.0 -> 0.5.1
• moq-stats: 0.2.0 -> 0.2.1
• moq-rtc: 0.3.0 -> 0.3.1
• moq-rtmp: 0.3.0 -> 0.3.1
• moq-srt: 0.3.0 -> 0.3.1
• moq-gst: 0.4.0 -> 0.4.1
• moq-room: 0.2.0 -> 0.2.1

Changelog

moq-json

0.4.1 - 2026-09-23

Added

• (ffi) add a TrackDemand handle and expose demand() on JSON producers (#3949)

moq-tokio

0.19.12 - 2026-09-23

Other

• update Cargo.toml dependencies

moq-video

0.0.27 - 2026-09-23

Fixed

• (ci) repair nightly builds hidden behind the first failure (#3956)

moq-uring

0.0.2 - 2026-09-23

Fixed

• (uring) close cancelled handshakes (#3932)
• (ci) repair nightly builds hidden behind the first failure (#3956)

moq-boy

0.5.1 - 2026-09-23

Other

• update Cargo.toml dependencies

moq-relay

0.15.1 - 2026-09-23

Fixed

• (ci) repair nightly builds hidden behind the first failure (#3956)
• (relay) follow usage-rs 6.11.1 moving env aliases under FlagMeta::extra (#4006)
• (relay) gate the per-worker accept loop on _quic (#3968)

Other

• (drill) retarget mutations after the dev merge (#3953)
• (quest) return to milestones (#3962)

moq-transcode

0.0.21 - 2026-09-23

Other

• update Cargo.toml dependencies

moq-cli

0.12.1 - 2026-09-23

Fixed

• (ci) repair nightly builds hidden behind the first failure (#3956)

moq-ffi

0.4.1 - 2026-09-23

Added

• (ffi) add a TrackDemand handle and expose demand() on JSON producers (#3949)

hang

0.21.1 - 2026-09-23

Other

• updated the following local packages: moq-tokio

moq-mux

0.10.1 - 2026-09-23

Other

• updated the following local packages: moq-json, hang

moq-audio

0.0.27 - 2026-09-23

Other

• updated the following local packages: hang, moq-mux

libmoq

0.6.1 - 2026-09-23

Other

• updated the following local packages: moq-json, moq-tokio, moq-video, hang, moq-mux, moq-audio

moq-hls

0.5.1 - 2026-09-23

Other

• updated the following local packages: moq-tokio, hang, moq-mux

moq-stats

0.2.1 - 2026-09-23

Other

• updated the following local packages: moq-json

moq-rtc

0.3.1 - 2026-09-23

Other

• updated the following local packages: moq-tokio, hang, moq-mux

moq-rtmp

0.3.1 - 2026-09-23

Other

• updated the following local packages: moq-tokio, hang, moq-mux

moq-srt

0.3.1 - 2026-09-23

Other

• updated the following local packages: hang, moq-mux

moq-gst

0.4.1 - 2026-09-23

Other

• updated the following local packages: moq-tokio, hang, moq-mux

moq-room

0.2.1 - 2026-09-23

Other

• updated the following local packages: moq-json, moq-tokio

---

This PR was generated with release-plz.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d5854dc4f5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Include moq-e2ee's pending changes in the release

This lock update moves moq-e2ee onto kio 0.6 and moq-net 0.3, but the crate remains at 0.0.1 and its changelog still leaves the breaking moq-e2ee-00 rewrite under Unreleased, below a dated 0.0.1 entry describing the obsolete moq-e2ee-01 API. If 0.0.1 was already published, the changed crate cannot be republished; if it was not, the initial release will carry inaccurate release notes and omit its actual API changes. Version and roll the pending changelog into this release.

AGENTS.md reference: AGENTS.md:L26-L27

Useful? React with 👍 / 👎.

[kixelated]

Verdict: ITERATE

Looks like a normal release-plz automation PR in intent: package bump list in the body, Cargo.lock refresh (lru 0.18.4→0.18.5), and changelog work for moq-tokio. Positive as a release vehicle once the notes are clean.

Complexity is fine for bot release automation. However, rs/moq-tokio/CHANGELOG.md already had duplicate ## [0.19.11] sections on main, and this PR inserts a third overlapping 0.19.11 block (now including #3941) above the prior ones. That is not a trustworthy release note for a tag that Cargo.toml already pins at 0.19.11.

Before merge: collapse to a single 0.19.11 section (or bump if these notes were meant for a newer version), drop the duplicated historical bullets, and confirm the multi-crate version list in the PR body matches what this commit actually releases (this diff only touches the lockfile and one changelog). After that cleanup, MERGE is appropriate; no alternative approach needed beyond fixing the generated notes.

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