chore: release

[moq-bot]

🤖 New release

• moq-net: 0.3.10 -> 0.3.11 (✓ API compatible changes)
• hang: 0.21.11 -> 0.21.12 (✓ API compatible changes)
• moq-mux: 0.10.11 -> 0.10.12 (✓ API compatible changes)
• moq-tokio: 0.19.23 -> 0.19.24 (✓ API compatible changes)
• moq-uring: 0.0.12 -> 0.0.13 (✓ API compatible changes)
• moq-boy: 0.5.12 -> 0.5.13
• moq-hls: 0.5.11 -> 0.5.12 (✓ API compatible changes)
• moq-relay: 0.17.2 -> 0.17.3 (✓ API compatible changes)
• moq-rtmp: 0.3.11 -> 0.3.12 (✓ API compatible changes)
• moq-transcode: 0.1.10 -> 0.1.11 (✓ API compatible changes)
• moq-cli: 0.14.2 -> 0.14.3
• moq-gst: 0.4.12 -> 0.4.13 (✓ API compatible changes)
• moq-json: 0.5.8 -> 0.5.9
• moq-binary: 0.1.10 -> 0.1.11
• moq-loc: 0.2.19 -> 0.2.20
• moq-audio: 0.1.10 -> 0.1.11
• moq-video: 0.1.10 -> 0.1.11
• libmoq: 0.6.12 -> 0.6.13
• moq-archive: 0.0.11 -> 0.0.12
• moq-stats: 0.2.12 -> 0.2.13
• moq-rtc: 0.3.12 -> 0.3.13
• moq-srt: 0.3.11 -> 0.3.12
• moq-e2ee: 0.0.11 -> 0.0.12
• moq-ffi: 0.4.12 -> 0.4.13
• moq-room: 0.2.11 -> 0.2.12

Changelog

moq-net

0.3.11 - 2026-10-11

Fixed

• (net) a duplicate group stream still counts toward the end
• (net) count a group stream whose group a fetch cached
• (net) a feed fetch waits out a reordered group
• (net) hold a fetch for a feed that opens alongside it
• (net) drop a feed-held fetch its caller abandoned
• (hls) a recorder cursor records a publisher without FETCH (backport fix(hls): a recorder cursor records a publisher without FETCH #5209)
• (net) move open IETF group streams on a priority update
• (net) read each IETF uni stream's type in its own task (backport fix(net): serve held groups to a cross-relay FETCH on any peer link #5086)
• (net) an ended track expires a shared group unless it is a live edge
• (net) a warm copy's expiry no longer aborts the relay's latest group
• (net) accept a clear FIRST_OBJECT that starts at object 0 (backport fix(net): accept a clear FIRST_OBJECT that starts at object 0 #5027) (#5069)

Other

• Merge pull request fix(net): backport complete namespace fills #5225 from moq-dev/quest/m1/release-backports/namespace-fill
• Merge pull request fix(net): backport quiet catalog floor clearing #5228 from moq-dev/quest/m1/release-backports/catalog-floor
• Merge pull request fix(net): backport FETCH requester FIN semantics #5230 from moq-dev/quest/m1/release-backports/fetch-fin
• Merge pull request fix(net): follow-ups to #5133 (deferred FIN on drop, reprioritize open group streams) #5164 from moq-dev/backport/ietf-fin-review-followups
• (net) an unacknowledged FIN follows priority updates
• Merge pull request fix(net): give an anonymous dial its own hop (backport #5025) #5126 from moq-dev/backport/anonymous-dial-hop
• Merge pull request fix(net): keep IETF subscriptions alive after a request FIN (backport #4658) #5133 from moq-dev/backport/ietf-fin-keeps-subscription
• Merge pull request fix(net): accept an End of Group status on a marked subgroup stream (backport #5081) #5127 from moq-dev/backport/end-of-group-status
• Merge pull request fix(net): draft-22 LOCATION_FILTER carries its Location Filter Type (backport #5080) #5094 from moq-dev/quest/m0/release-22/location-filter
• (net) pin when ended tracks sharing a group release it

hang

0.21.12 - 2026-10-11

Fixed

• (hang) accept AV1 profile 2 codec strings (#5064)

moq-mux

0.10.12 - 2026-10-11

Fixed

• (mux) keep the last good parameter sets when refusing a TS access unit
• (mux) refuse damaged TS units without ending ingest (backport fix(mux): refuse damaged TS units without ending ingest #4733)

Other

• Merge pull request fix(mux): refuse damaged TS units without ending ingest (backport #4733) #5124 from moq-dev/backport/ts-damaged-units
• (mux) note the per-PES parameter set rollback, and drop 'refused whole'

moq-tokio

0.19.24 - 2026-10-11

Fixed

• (tokio) keep a deferred FIN when a send stream drops mid-watch
• (net) keep IETF subscriptions alive after a request FIN (backport fix(net): keep IETF requests alive after FIN #4658)

Other

• Merge pull request fix(net): give an anonymous dial its own hop (backport #5025) #5126 from moq-dev/backport/anonymous-dial-hop

moq-uring

0.0.13 - 2026-10-11

Other

• update Cargo.toml dependencies

moq-boy

0.5.13 - 2026-10-11

Other

• update Cargo.lock dependencies

moq-hls

0.5.12 - 2026-10-11

Fixed

• (hls) a recorder cursor records a publisher without FETCH (backport fix(hls): a recorder cursor records a publisher without FETCH #5209)
• (hls) retain init decoded from completed segments (#4840)

moq-relay

0.17.3 - 2026-10-11

Other

• update Cargo.lock dependencies

moq-rtmp

0.3.12 - 2026-10-11

Fixed

• (rtmp) reassemble interleaved chunk streams independently (#4735)

moq-transcode

0.1.11 - 2026-10-11

Fixed

• (transcode) refuse a fetch that starts mid-group (#4812)

moq-cli

0.14.3 - 2026-10-11

Other

• update Cargo.lock dependencies

moq-gst

0.4.13 - 2026-10-11

Fixed

• (moq-mux) configure H.265 from the SPS head when scuffle_h265 refuses the rest (#4924)

moq-json

0.5.9 - 2026-10-11

Other

• updated the following local packages: moq-net

moq-binary

0.1.11 - 2026-10-11

Other

• updated the following local packages: moq-net

moq-loc

0.2.20 - 2026-10-11

Other

• updated the following local packages: moq-net

moq-audio

0.1.11 - 2026-10-11

Other

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

moq-video

0.1.11 - 2026-10-11

Other

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

libmoq

0.6.13 - 2026-10-11

Other

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

moq-archive

0.0.12 - 2026-10-11

Other

• updated the following local packages: moq-net

moq-stats

0.2.13 - 2026-10-11

Other

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

moq-rtc

0.3.13 - 2026-10-11

Other

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

moq-srt

0.3.12 - 2026-10-11

Other

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

moq-e2ee

0.0.12 - 2026-10-11

Other

• updated the following local packages: moq-net

moq-ffi

0.4.13 - 2026-10-11

Other

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

moq-room

0.2.12 - 2026-10-11

Other

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

---

This PR was generated with release-plz.

[kixelated]

Automated review of #4944 (release-plz), head 7a54baf6b701c7c8dc5f9acce02ffff5b15e5306

This is the same follow-up-PR pattern as #4867's first head. The PR doesn't actually bump anything. All 9 version bumps listed in the body (moq-tokio 0.19.23, moq-relay 0.17.2, moq-stats 0.2.12, and the rest) already landed on release in #4867 (merged 12:06 PT, commit b084269d). The real diff is a transitive lockfile refresh plus a second moq-tokio changelog section.

Blocking

1. Duplicate 0.19.23 heading in rs/moq-tokio/CHANGELOG.md. On head, the file has two ## [0.19.23] ... - 2026-10-06 sections (lines 10 and 20). The new one repeats the fix(moq-tokio): finite default connection receive window (backport #4605) #4858 fix and adds release ([#4867]) under "Other", which is the release commit listing itself as a change. Merging this leaves a broken changelog for a version that is about to go to crates.io.
   • Cause, now confirmed by timing: rs/justfile's release recipe runs release-plz release-pr before release-plz release (same order on main, line 299). Release RS run 37516509658 for b084269d started its Plz job at 12:19 PT and opened this PR at 12:24 PT, while moq-tokio-v0.19.23 was still untagged and crates.io still showed 0.19.22. So release-pr treated the chore: release #4867 commit as a new unreleased change. Swapping the two lines (publish first, then open the next release PR) should stop this phantom PR from appearing after every release merge. This is the second time in two days.
   • Fix for this PR: close it once the in-flight run finishes publishing, and let release-plz regenerate it on the next real change. Or delete lines 16-25 of rs/moq-tokio/CHANGELOG.md if you want to keep the lockfile refresh.

Non-blocking

2. The PR body is stale and misleading. It repeats chore: release #4867's 9-crate bump list and changelogs, none of which this diff contains.
3. The lockfile bumps look fine. either 1.19.0, h2 0.4.20, hyper 1.12.0, jiff/jiff-static 0.2.38, jiff-tzdb 0.1.9, the usage-* 6.12.1 family, and zeroize 1.9.1 were all published today, none are yanked, and the checksums match crates.io. They're transitive and can ride along with the next real release.
4. CI is still pending (Check, Test, WASM, Android, Swift, OBS, Windows, macOS).

Verdict: ITERATE. Drop the duplicate changelog section or close this PR. Separately, reorder release-plz release before release-pr in rs/justfile.

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

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: 7a54baf

[P2] Remove the duplicate release entry before landing. rs/moq-tokio/CHANGELOG.md:20–24 adds a second 0.19.23 section, repeating the existing heading/fix at lines 10–14. This PR has no crate-version changes: its actual diff is a transitive Cargo.lock refresh plus the duplicated changelog, although the body advertises nine new releases. Regenerate after publishing the existing release, or retain only the intended dependency update with an accurate description.

This independently confirms the existing finding in #4944 (comment); no duplicate inline thread added. Direction: a dependency refresh can stand alone, but this should not be treated as a fresh nine-crate release.

Verification: inspected both changed files, the pinned moq-tokio manifest/changelog, release recipe and prior discussion. No build or publishing command run. Exact-head Check, Test and the returned platform checks passed; those checks do not resolve the duplicated release metadata.

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: 0d1e051

No new actionable findings in the 52-file release delta.

Fixed since the previous review: rs/moq-tokio/CHANGELOG.md:10–20 now contains a genuine 0.19.24 entry and a single 0.19.23 entry. The advertised 25 crate-version bumps agree with the manifest changes, applicable workspace dependency versions, Cargo.lock entries and changelog headings.

Direction: this is now a coherent patch-release update. I separated changes already on the release branch from this PR's metadata/dependency changes; the PR itself introduces no source/API/wire-format edits. The previously discussed release-pr-before-release ordering in rs/justfile:262–265 remains unchanged and outside this diff.

Verification: inspected every changed-file patch, pinned workspace manifest/lockfile, the complete moq-tokio changelog, release recipe and prior reviews. No build, runtime test or publishing command run; registry availability was not independently checked. At the final state check, Android and WASM passed, Check was queued, and Swift/OBS/Platform were running. Require completed current CI before landing.

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: 9597646

No new actionable findings in the cumulative release delta since 0d1e051.

Cargo.lock:9495–9498 now updates uuid 1.27.0 → 1.28.0, within the unchanged Cargo.toml:233 requirement; the remaining lockfile patch is unchanged. All 25 advertised crate bumps still agree across manifest patches, applicable workspace dependencies, lock entries and changelog headings. The duplicate moq-tokio release entry remains fixed.

Direction: coherent patch-release metadata. Accounting for intervening release-branch changes, this PR introduces no source/API/wire-format edits; the expanded changelogs describe the refreshed base.

Verification: compared all 52 release-file patches with the last reviewed commit and checked pinned workspace metadata, the uuid lock entry, moq-tokio changelog and prior reviews. No build, runtime or publishing commands run; registry availability/checksums were not independently verified. Current-head CI remains queued/running; require completed checks before landing.

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: 9905e42

No new actionable findings in the release metadata/dependency delta.

Since the last review at 9597646, Cargo.lock adds cc 1.6.0 → 1.7.0 (lines 1017–1020), smallvec 1.16.2 → 1.16.3 (8053–8056), and syn 3.0.6 → 3.0.7 (8487–8490). All version-qualified syn references were updated consistently. The 25 advertised crate bumps still agree across manifests, applicable workspace dependencies, lock entries and changelog headings.

Direction: coherent patch-release metadata. I separated changes already on the refreshed release base from this PR; its own 52-file delta contains no source/API/wire-format edits.

Verification: compared every release-file patch against the previous review and inspected the pinned workspace manifest and complete lockfile. No build/runtime/publishing commands run; upstream dependency behavior, registry availability and checksums were not independently verified. Current-head CI remains pending; require completed checks before landing.

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: ee7094d

No new actionable findings in this release refresh.

Since review 5477239479, Cargo.lock:4538–4594 and 9850–9853 update moq-noq, moq-noq-proto, moq-noq-udp and web-transport-moq together from 1.3.4 to 1.3.5. The unchanged workspace requirements allow these patch versions; the fork's dependency references remain consistent and separate from upstream noq. All 25 advertised crate bumps still match their manifests, workspace references, lock entries and changelog headings.

Direction: coherent patch-release metadata. Fifty of 52 file patches are identical to the previous review; the other change is a moq-net changelog entry for a fix already on the refreshed release base. The PR itself adds no source/API/wire-format edits.

Verification: compared all release patches, inspected the complete pinned lockfile and workspace/moq-tokio/moq-uring manifests. No build/runtime/publishing commands run; upstream dependency behavior, registry availability and checksums were not independently verified. Current-head CI is queued/running; require completed checks before landing.

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: ce76937

No new actionable findings in the release refresh.

Since ee7094d, Cargo.lock:7779–7782 updates serde_json 1.0.151 → 1.0.152, within Cargo.toml:213's unchanged requirement. Every other lockfile package block is identical. All 25 crate bumps still match their manifest patches, applicable workspace references, lock entries and changelog headings; the duplicate moq-tokio release entry remains fixed.

Direction: coherent patch-release metadata. Accounting for the refreshed release base, this PR's 52-file diff contains no source/API/wire-format edits. The remaining changes refresh generated changelogs.

Verification: compared both release commits' file patches and complete lockfiles, and inspected pinned workspace metadata and the moq-tokio changelog. No build/runtime/publishing commands run; upstream dependency behavior, registry availability and checksums were not independently verified. Current-head CI is running; require completed checks before landing.

(Written by OpenAI)