From 9ded14054c5581f24c894ed7d42d5c20a57ecf37 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 17:04:15 -0700 Subject: [PATCH 1/3] chore(quest): claim quest/m0/backport-ietf-close-codes.md Quest-Claim: 629a15305c10555b From 97c5769a90f8952543b15f8b4512be2892fe0f12 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 17:11:04 -0700 Subject: [PATCH 2/3] chore(quest): track the prepared IETF close-code backport Co-Authored-By: GPT-6 --- quest/m0/backport-ietf-close-codes.md | 30 ++++++++++++--------------- 1 file changed, 13 insertions(+), 17 deletions(-) diff --git a/quest/m0/backport-ietf-close-codes.md b/quest/m0/backport-ietf-close-codes.md index 2926db29294..8ba0df4a863 100644 --- a/quest/m0/backport-ietf-close-codes.md +++ b/quest/m0/backport-ietf-close-codes.md @@ -1,26 +1,22 @@ -# [S] Backport the IETF close-code fixes to release +# [S] Merge and publish the IETF close-code backport ## Goal -`@moq/net` on `release` closes a moq-transport session with the right error for -the three cases [moq-dev/moq#6899](https://github.com/moq-dev/moq/pull/6899) -fixed on main, and publishes a patch release. +[moq-dev/moq#6959](https://github.com/moq-dev/moq/pull/6959) merges to +`release`, and a patch of `@moq/net` containing it publishes. Confirm the +published package includes the three protocol-violation close fixes from +[moq-dev/moq#6899](https://github.com/moq-dev/moq/pull/6899). ## Plan -Decided 2026-10-27 (maintainer): one PR against `release` per backport, in m0, -since these are hostile-input fixes in shipped packages. +The release-targeted implementation is prepared in #6959, with six regression +cases covering drafts 18 and 22: initial REQUEST_UPDATE, unsolicited +PUBLISH_NAMESPACE, and a track alias reused for different tracks. +The main-only advertisement budgets and SUBSCRIBE_TRACKS changes do not apply. -The bugs on `release` (as of 6ce67943f7): - -- `js/net/src/ietf/connection.ts:265`: a REQUEST_UPDATE as the initial message - aborts only the stream instead of closing the session with a protocol violation. -- `connection.ts:314-317`: an unsolicited PUBLISH_NAMESPACE logs and closes - cleanly instead of with an error. -- `subscriber.ts:807`: a `DuplicateTrackAlias` closes the session without its - error code. - -The announce-slot and SUBSCRIBE_TRACKS parts of #6899 are main-only and do not -apply. Port the regression tests that cover the three cases. +Decided 2026-10-27 (maintainer): PR creation only in this session; merging +and publication remain for a later authorized session. No package version was +bumped. Once the release PR has merged and its patch has published, delete +this quest and its links on main. Public API: none. Wire: close codes only, matching main. From df03bee926c2342c6ec5300a8f1c8ecace28293e Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 23:29:32 -0700 Subject: [PATCH 3/3] chore(quest): finish the IETF close-code release backport @moq/net 0.4.7 on npm carries moq-dev/moq#6959. Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 1 - quest/m0/backport-ietf-close-codes.md | 22 ---------------------- 2 files changed, 23 deletions(-) delete mode 100644 quest/m0/backport-ietf-close-codes.md diff --git a/quest/m0/README.md b/quest/m0/README.md index 8357acee985..95417f64535 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -22,7 +22,6 @@ edge, which embeds moq-relay; it moved there on 2026-09-28. - [Nightly passes on main](/quest/m0/nightly/README.md) - the scheduled Nightly passes end to end, so red means a new break - [Release shutdown backport](/quest/m0/ffi-shutdown-backport.md) - `release` publishes a non-breaking moq-ffi with an async `drain()` and qmux sessions on the QUIC stream limit -- [Backport IETF close codes](/quest/m0/backport-ietf-close-codes.md) - `@moq/net` on `release` closes moq-transport sessions with the right error for three hostile cases - [Backport @moq/flate bounds](/quest/m0/backport-flate-budget.md) - `@moq/flate` on `release` stops inflating past its cap and stops pinning pako scratch - [Backport MKV, FLV, and VP9 import fixes](/quest/m0/backport-mux-import.md) - moq-mux on `release` refuses malformed imports instead of wrapping, panicking, or dropping tracks - [Backport the frame-start refusal](/quest/m0/backport-frame-start.md) - `@moq/net` on `release` refuses a nonzero lite frame start instead of misnumbering frames diff --git a/quest/m0/backport-ietf-close-codes.md b/quest/m0/backport-ietf-close-codes.md deleted file mode 100644 index 8ba0df4a863..00000000000 --- a/quest/m0/backport-ietf-close-codes.md +++ /dev/null @@ -1,22 +0,0 @@ -# [S] Merge and publish the IETF close-code backport - -## Goal - -[moq-dev/moq#6959](https://github.com/moq-dev/moq/pull/6959) merges to -`release`, and a patch of `@moq/net` containing it publishes. Confirm the -published package includes the three protocol-violation close fixes from -[moq-dev/moq#6899](https://github.com/moq-dev/moq/pull/6899). - -## Plan - -The release-targeted implementation is prepared in #6959, with six regression -cases covering drafts 18 and 22: initial REQUEST_UPDATE, unsolicited -PUBLISH_NAMESPACE, and a track alias reused for different tracks. -The main-only advertisement budgets and SUBSCRIBE_TRACKS changes do not apply. - -Decided 2026-10-27 (maintainer): PR creation only in this session; merging -and publication remain for a later authorized session. No package version was -bumped. Once the release PR has merged and its patch has published, delete -this quest and its links on main. - -Public API: none. Wire: close codes only, matching main.