chore: release

[moq-bot]

🤖 New release

• moq-net: 0.3.0 -> 0.3.1 (✓ API compatible changes)
• libmoq: 0.6.1 -> 0.6.2
• moq-relay: 0.15.1 -> 0.15.2 (✓ API compatible changes)
• moq-cli: 0.12.1 -> 0.12.2
• moq-ffi: 0.4.1 -> 0.4.2
• moq-json: 0.4.1 -> 0.4.2
• hang: 0.21.1 -> 0.21.2
• moq-binary: 0.1.0 -> 0.1.1
• moq-loc: 0.2.9 -> 0.2.10
• moq-mux: 0.10.1 -> 0.10.2
• moq-tokio: 0.19.12 -> 0.19.13
• moq-audio: 0.0.27 -> 0.0.28
• moq-video: 0.0.27 -> 0.0.28
• moq-archive: 0.0.1 -> 0.0.2
• moq-uring: 0.0.2 -> 0.0.3
• moq-boy: 0.5.1 -> 0.5.2
• moq-hls: 0.5.1 -> 0.5.2
• moq-stats: 0.2.1 -> 0.2.2
• moq-rtc: 0.3.1 -> 0.3.2
• moq-rtmp: 0.3.1 -> 0.3.2
• moq-srt: 0.3.1 -> 0.3.2
• moq-transcode: 0.0.21 -> 0.0.22
• moq-e2ee: 0.0.1 -> 0.0.2
• moq-gst: 0.4.1 -> 0.4.2
• moq-room: 0.2.1 -> 0.2.2

Changelog

moq-net

0.3.1 - 2026-09-24

Fixed

• (relay) keep only finished groups warm when a track goes idle (#3977)
• (net) don't end in-flight tracks when their broadcast ends (#4007)

Other

• rename in-repo smoke test to interop (#3963)

libmoq

0.6.2 - 2026-09-24

Other

• rename in-repo smoke test to interop (#3963)

moq-relay

0.15.2 - 2026-09-24

Fixed

• (relay) fix the lease deadline on tokio's clock and pause the outage test (#3969)

moq-cli

0.12.2 - 2026-09-24

Fixed

• (cli) play a retired audio rendition's tail alongside its replacement (#3966)

moq-ffi

0.4.2 - 2026-09-24

Other

• rename in-repo smoke test to interop (#3963)

moq-json

0.4.2 - 2026-09-24

Other

• updated the following local packages: moq-net

hang

0.21.2 - 2026-09-24

Other

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

moq-binary

0.1.1 - 2026-09-24

Other

• updated the following local packages: moq-net

moq-loc

0.2.10 - 2026-09-24

Other

• updated the following local packages: moq-net

moq-mux

0.10.2 - 2026-09-24

Other

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

moq-tokio

0.19.13 - 2026-09-24

Other

• updated the following local packages: moq-net

moq-audio

0.0.28 - 2026-09-24

Other

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

moq-video

0.0.28 - 2026-09-24

Other

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

moq-archive

0.0.2 - 2026-09-24

Other

• updated the following local packages: moq-net

moq-uring

0.0.3 - 2026-09-24

Other

• updated the following local packages: moq-net

moq-boy

0.5.2 - 2026-09-24

Other

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

moq-hls

0.5.2 - 2026-09-24

Other

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

moq-stats

0.2.2 - 2026-09-24

Other

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

moq-rtc

0.3.2 - 2026-09-24

Other

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

moq-rtmp

0.3.2 - 2026-09-24

Other

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

moq-srt

0.3.2 - 2026-09-24

Other

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

moq-transcode

0.0.22 - 2026-09-24

Other

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

moq-e2ee

0.0.2 - 2026-09-24

Other

• updated the following local packages: moq-net

Changed

• Profile moq-e2ee-00: every derivation is scoped to a publisher-minted Epoch, the last segment of the opaque broadcast path from Credential::path
• Credential::new(credential::Config { context, kid, secret }) takes the application-owned secret; Credential::generate, Pin, and the profile argument are gone
• Generation replaces Publication: clones share per-track claims and nothing is process-global; Name replaces PhysicalName
• track::Producer refuses a sequence below the next allocated one before encryption; datagram plaintext is capped at MAX_DATAGRAM_PLAINTEXT (1160 bytes)
• Failed opens count against the key's invocation budget

Removed

• Datagram retention and retransmission, the grouped duplicate window, the catalog module, and the stateless protect/open/nonce, HKDF, and raw key exports

moq-gst

0.4.2 - 2026-09-24

Other

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

moq-room

0.2.2 - 2026-09-24

Other

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

---

This PR was generated with release-plz.

[kixelated]

Verdict: RECONSIDER

This looks like post-release churn from release-plz, not a clean version bump.

What is wrong

• #3945 already released moq-tokio to 0.19.12 and was merged minutes before this opened.
• rs/moq-tokio/Cargo.toml is already 0.19.12 on both main and this branch; there is no version bump here.
• The only file change is rs/moq-tokio/CHANGELOG.md, and it inserts a second ## [0.19.12] ... - 2026-09-24 section above the existing ## [0.19.12] ... - 2026-09-23 block. Same version, two headers, different dates/notes.
• The PR body lists many crate bumps (hang, moq-json, moq-mux, …) that are not present in the diff.

Positive improvement? No. A duplicate changelog heading for an already-released version adds noise and can confuse consumers reading Keep a Changelog.

Worth the complexity? N/A — this is accidental automation output, not intentional design.

Different approach? Close this PR (or have release-plz regenerate after the prior release settles). If the #3945 note is worth keeping, fold it into the existing 0.19.12 section instead of minting a second one. Do not merge as-is.

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6fe18e41b4

ℹ️ 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]

Remove the duplicate 0.19.12 release entry

The preceding block already records version 0.19.12 with the identical comparison range, and the parent already has rs/moq-tokio/Cargo.toml at 0.19.12. Adding another heading for the same version assigns two different release notes and dates to one published version, so consumers cannot tell which notes belong to that release. Merge this note into the existing entry or reserve it for the next version bump.

Useful? React with 👍 / 👎.