Repository navigation
chore: release - #8378
chore: release#8378
Conversation
There was a problem hiding this comment.
ℹ️ The Rust release itself checks out. One release-completeness gap sits outside this diff.
Reviewed changes
moq-tokio0.19.36: the only source change being released, the IPv4-spelling GOAWAY fix fromf823d2ad5.- Seven dependent bumps:
libmoq,moq-boy,moq-relay,moq-rtc,moq-cli,moq-ffi,moq-gstmove a patch for the localmoq-tokioupdate, matching what each changelog records. - Workspace manifest and lockfile: root
Cargo.tomlpins follow the new versions; the lockfile churn (syn,crypto-bigint, ...) is the same routine registry drift the previous release PR carried. - Changelogs: one dated entry added at the top of each package,
## [Unreleased]sections retained.
I verified the release is complete on the Rust side: 92e6e53c8 (2026-11-08 release) to adc9f4651 contains only the backport, every published consumer of moq-tokio is bumped, no published crate pins an explicit version on a bumped crate, and moq-bench is publish = false.
ℹ️ The JS half of the same backport stays unpublished
The accepted fix touches both rs/moq-tokio/src/connection.rs and js/net/src/connection/goaway.ts, but only moq-tokio is released here. js/net/package.json is still 0.4.7 (last bumped 2026-10-27), and @moq/net@0.4.7 is already on npm, so js/common/release.ts skipped the publish triggered by the #8346 merge. Browser clients keep the buggy isLocal until a version bump lands on release.
Technical details
# Unreleased JS half of the GOAWAY backport
## Affected sites
- `js/net/src/connection/goaway.ts` - fix merged on `release` in f823d2ad5, version never bumped
- `js/net/package.json:4` - still `0.4.7`
- `js/common/release.ts:22-25` - exits early when the exact version is already on npm
- `.github/workflows/release-js.yml:8-12` - publishes on push to `release` touching `js/**`
## Required outcome
- Ship `@moq/net` with the `f823d2ad5` JS change, via the usual separate `chore(js): bump @moq/net on release` PR merged to `release` (not this generated PR).
## Evidence
- `gh pr list --base release --state open` returns only this PR, so no bump PR is queued.
- `registry.npmjs.org/@moq/net/latest` reports `0.4.7`, whose `gitHead` predates the fix.
## Open questions for the human
- Whether the JS release is intentionally batched with a later `release` cut instead of shipping alongside `moq-tokio@0.19.36`.(Written by DeepSeek V4.1 Flash 1017)
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head: da03a529239e98c971a8aff0eeb33c9794d94b30.
No additional actionable findings in this generated Rust release diff. The eight patch versions, inherited workspace requirements, and changelog entries consistently package the GOAWAY backport already on release. This PR introduces no source-level API or wire changes. Keeping it focused on the existing release-plz flow is appropriate.
Verification: GitHub-only static inspection of the diff, affected manifests, release configuration/workflow, and backport source/test context. No local builds or tests were run; Check, Test, and platform jobs are still running, so this is not CI or runtime verification.
(Written by OpenAI)
da03a52 to
b1a90aa
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Added
moq-net0.3.23 to the cut: the refused-replacement fix from #8469 and its regression test now ship, with matchingFixedandOtherchangelog entries. - Cascaded 23 dependent crates:
hang,moq-json,moq-binary,moq-loc,moq-mux,moq-audio,moq-video,libmoq,moq-archive,moq-uring,moq-boy,moq-hls,moq-stats,moq-relay,moq-rtc,moq-rtmp,moq-srt,moq-transcode,moq-cli,moq-e2ee,moq-ffi,moq-gst, andmoq-roomeach move a patch and record their updated local deps. - Updated workspace pins and regenerated
Cargo.lock: the rootCargo.tomlfollows every new version, the lockfile carries routine registry patch bumps and drops the unusedpin-utils, andcargo metadata --locked --offlinevalidates it. - Kept
moq-tokio0.19.36 in the release: the GOAWAY backport remains in the cut, with its changelog date moved to 2026-11-11.
Verification: since 92e6e53c8, release contains only f823d2ad5, 83506a30e, and 861b3b237; every published crate that depends on a bumped crate is itself bumped (moq-bench and moq-wasm are publish = false); manifest versions, changelog headings, and lockfile entries agree for all 25 packages.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

🤖 New release
moq-net: 0.3.22 -> 0.3.23 (✓ API compatible changes)moq-tokio: 0.19.35 -> 0.19.36 (✓ API compatible changes)moq-json: 0.5.20 -> 0.5.21hang: 0.21.23 -> 0.21.24moq-binary: 0.1.22 -> 0.1.23moq-loc: 0.2.31 -> 0.2.32moq-mux: 0.10.23 -> 0.10.24moq-audio: 0.1.22 -> 0.1.23moq-video: 0.1.22 -> 0.1.23libmoq: 0.6.24 -> 0.6.25moq-archive: 0.0.23 -> 0.0.24moq-uring: 0.0.24 -> 0.0.25moq-boy: 0.5.25 -> 0.5.26moq-hls: 0.5.23 -> 0.5.24moq-stats: 0.2.24 -> 0.2.25moq-relay: 0.17.15 -> 0.17.16moq-rtc: 0.3.24 -> 0.3.25moq-rtmp: 0.3.23 -> 0.3.24moq-srt: 0.3.23 -> 0.3.24moq-transcode: 0.1.22 -> 0.1.23moq-cli: 0.14.15 -> 0.14.16moq-e2ee: 0.0.24 -> 0.0.25moq-ffi: 0.4.24 -> 0.4.25moq-gst: 0.4.25 -> 0.4.26moq-room: 0.2.23 -> 0.2.24Changelog
moq-netmoq-tokiomoq-jsonhangmoq-binarymoq-locmoq-muxmoq-audiomoq-videolibmoqmoq-archivemoq-uringmoq-boymoq-hlsmoq-statsmoq-relaymoq-rtcmoq-rtmpmoq-srtmoq-transcodemoq-climoq-e2eemoq-ffimoq-gstmoq-roomThis PR was generated with release-plz.