Skip to content

chore: release - #7936

Merged
kixelated merged 2 commits into
releasefrom
release-plz-2026-11-05T06-34-53Z
Nov 5, 2026
Merged

kixelated merged 2 commits into
releasefrom
release-plz-2026-11-05T06-34-53Z

Conversation

@moq-bot

@moq-bot moq-bot Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

🤖 New release

  • moq-net: 0.3.20 -> 0.3.21 (✓ API compatible changes)
  • moq-relay: 0.17.12 -> 0.17.13 (✓ API compatible changes)
  • moq-json: 0.5.18 -> 0.5.19
  • hang: 0.21.21 -> 0.21.22
  • moq-binary: 0.1.20 -> 0.1.21
  • moq-loc: 0.2.29 -> 0.2.30
  • moq-mux: 0.10.21 -> 0.10.22
  • moq-tokio: 0.19.33 -> 0.19.34
  • moq-audio: 0.1.20 -> 0.1.21
  • moq-video: 0.1.20 -> 0.1.21
  • libmoq: 0.6.22 -> 0.6.23
  • moq-archive: 0.0.21 -> 0.0.22
  • moq-uring: 0.0.22 -> 0.0.23
  • moq-boy: 0.5.22 -> 0.5.23
  • moq-hls: 0.5.21 -> 0.5.22
  • moq-stats: 0.2.22 -> 0.2.23
  • moq-rtc: 0.3.22 -> 0.3.23
  • moq-rtmp: 0.3.21 -> 0.3.22
  • moq-srt: 0.3.21 -> 0.3.22
  • moq-transcode: 0.1.20 -> 0.1.21
  • moq-cli: 0.14.12 -> 0.14.13
  • moq-e2ee: 0.0.21 -> 0.0.22
  • moq-ffi: 0.4.22 -> 0.4.23
  • moq-gst: 0.4.22 -> 0.4.23
  • moq-room: 0.2.21 -> 0.2.22
Changelog

moq-net

0.3.21 - 2026-11-05

Fixed

  • (net) withdraw IETF advertisements without send credit on release

Other

  • Merge remote-tracking branch 'origin/release' into HEAD

moq-relay

0.17.13 - 2026-11-05

Fixed

  • (relay) backport HTTP response and ops-listener hardening

moq-json

0.5.19 - 2026-11-05

Other

  • updated the following local packages: moq-net

hang

0.21.22 - 2026-11-05

Other

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

moq-binary

0.1.21 - 2026-11-05

Other

  • updated the following local packages: moq-net

moq-loc

0.2.30 - 2026-11-05

Other

  • updated the following local packages: moq-net

moq-mux

0.10.22 - 2026-11-05

Other

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

moq-tokio

0.19.34 - 2026-11-05

Other

  • updated the following local packages: moq-net

moq-audio

0.1.21 - 2026-11-05

Other

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

moq-video

0.1.21 - 2026-11-05

Other

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

libmoq

0.6.23 - 2026-11-05

Other

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

moq-archive

0.0.22 - 2026-11-05

Other

  • updated the following local packages: moq-net

moq-uring

0.0.23 - 2026-11-05

Other

  • updated the following local packages: moq-net

moq-boy

0.5.23 - 2026-11-05

Other

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

moq-hls

0.5.22 - 2026-11-05

Other

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

moq-stats

0.2.23 - 2026-11-05

Other

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

moq-rtc

0.3.23 - 2026-11-05

Other

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

moq-rtmp

0.3.22 - 2026-11-05

Other

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

moq-srt

0.3.22 - 2026-11-05

Other

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

moq-transcode

0.1.21 - 2026-11-05

Other

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

moq-cli

0.14.13 - 2026-11-05

Other

  • updated the following local packages: moq-relay, hang, moq-mux, moq-tokio, moq-audio, moq-video, moq-hls, moq-rtc, moq-rtmp, moq-srt, moq-transcode

moq-e2ee

0.0.22 - 2026-11-05

Other

  • updated the following local packages: moq-net

moq-ffi

0.4.23 - 2026-11-05

Other

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

moq-gst

0.4.23 - 2026-11-05

Other

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

moq-room

0.2.22 - 2026-11-05

Other

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


This PR was generated with release-plz.

@kixelated kixelated left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review by review (OpenAI)

Reviewed commit: b650028

No actionable findings. Relay and CLI versions, workspace requirements, lock entries and changelogs are consistent; the dependency refresh follows the existing release configuration. The narrow patch release is appropriate to the backport described.

Verification: GitHub-only static review. I did not run builds, tests or registry validation; exact-head jobs were queued or running when inspected.

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

  • Version bump for moq-relay: 0.17.12 → 0.17.13, with the changelog crediting the HTTP response and ops-listener hardening backport.
  • Version bump for moq-cli: 0.14.12 → 0.14.13, tracking its dependency on moq-relay.
  • Workspace dependency update: root Cargo.toml moves moq-relay to 0.17.13; moq-cli inherits it via workspace = true.
  • Regenerated Cargo.lock: matching package versions plus compatible transitive bumps (toml 1.2.0, toml_edit 0.25.18, winnow 1.0.5, moq-vaapi 0.1.1), consistent with .release-plz.toml dependencies_update = true.

I verified the changelog claim against the release branch: beeb23df7 (merged in #7920) is present, so the note is accurate. Version strings match between Cargo.toml, CHANGELOG.md, and Cargo.lock, no other crate pins moq-relay at an explicit version, and the dependency constraints (toml = "1.1", moq-vaapi = "0.1.0") still admit the resolved versions.

Pullfrog  | View workflow run | Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T06-34-53Z branch from b650028 to e6295c2 Compare November 5, 2026 08:02

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

Reviewed the delta from b650028cc to e6295c213, which is a rebase onto the newer release branch plus a wider release-plz regeneration.

  • Release scope widened from 2 to 25 crates: moq-net 0.3.21 now carries the "withdraw IETF advertisements without send credit" fix, and every published crate that (transitively) depends on a bumped crate got a patch bump with a "updated the following local packages" changelog entry.
  • moq-relay 0.17.13 retained: the HTTP response / ops-listener hardening backport note is still accurate for this release.
  • Workspace and per-crate manifests: all root workspace dep versions and each crate Cargo.toml version match the new release, including moq-cli, moq-ffi, libmoq, moq-gst, and moq-room.
  • Cargo.lock regenerated: the diff is now only name / version lines; the incidental transitive bumps from the first revision are gone.

I checked every crate version against the root workspace deps, Cargo.lock, and the latest CHANGELOG.md heading, and confirmed that every published crate depending on a bumped crate was itself bumped (only the publish = false moq-bench and moq-wasm are excluded). cargo metadata --locked --offline --no-deps succeeds, and the PR body release list matches the 25 bumped crates exactly.

(Written by DeepSeek V4.1 Flash 1017)

Pullfrog  | View workflow run | Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T06-34-53Z branch from e6295c2 to 9efcf3f Compare November 5, 2026 21:36

@kixelated kixelated left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review by review (OpenAI)

Reviewed commit: 9efcf3f
Base: dc3478a

No actionable findings. Compared with my previous review of b650028, this expands the release from 2 to 25 crates and refreshes dependencies. All 25 crate versions agree with their lock entries, changelog headings, PR release list and applicable workspace requirements. The dependency refresh follows the existing release-plz configuration; there were no prior findings to carry forward.

Direction: the generated patch-release approach remains appropriate. The diff against the current release base contains only release metadata and dependency updates, with no new source-level API or wire changes.

Verification: GitHub-only static review. I did not run builds, tests or registry validation. Exact-head Check and the latest Release gate workflows were still running when rechecked.

(Written by OpenAI)

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ No critical issues. One release-notes gap inline.

Reviewed changes

Reviewed the delta from e6295c2 to 9efcf3f, where the branch picked up the new release tip and release-plz regenerated.

  • Base advanced to the joined-head backport: dc3478a86 merged #7680's moq-net cache-miss FETCH race fix into release, so those fixes ship in this cut.
  • Regenerated moq-net changelog: 0.3.21 only gained an ### Other line recording the merge commit, with no ### Fixed entries for the shipped fix commits.
  • Lockfile refreshed again: enum-assoc 1.4.2, futures-buffered 0.2.14 (now pulling fixedbitset 0.5.7), generator 0.8.12, mime 0.3.18, winnow 1.0.5, toml_edit 0.25.18, plus a second windows-core / windows-link / windows-result / windows-strings 0.100.0 family alongside 0.62.2.

I re-checked version consistency at this head: every root workspace dep matches its crate's Cargo.toml, every Cargo.lock package version matches its crate, every bumped crate's latest CHANGELOG.md heading matches its version (only pre-existing moq-v4l differs, untouched here), and cargo metadata --locked --offline --no-deps succeeds. CI at this head was still running; the failing Release gate is the sibling-workflow gate, not a build or test failure.

Pullfrog  | Fix all ➔ | Fix 👍s ➔ | View workflow run | Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

Comment thread rs/moq-net/CHANGELOG.md Resolved
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@kixelated kixelated left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review by review (OpenAI)

Reviewed commit: a50cda6

No actionable findings in the delta since 9efcf3f. The only change replaces merge noise in moq-net's 0.3.21 changelog with the joined-head FETCH and PUBLISH_DONE-grace fixes. Both descriptions match the implementation already merged into the release base by #7680, addressing the release-notes gap raised in the intervening review.

Direction: keep this focused changelog correction. No implementation, API, wire, or version changes were added in this round.

Verification: GitHub-only static comparison against the previous reviewed head and merged backport. No builds or tests run; exact-head Check is running and Release gate is pending.

(Written by OpenAI)

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

Reviewed the delta from 9efcf3f96 to a50cda650, a single docs commit on release-plz-2026-11-05T06-34-53Z.

  • moq-net 0.3.21 release notes completed: rs/moq-net/CHANGELOG.md now lists the shipped joined-head cache-miss fixes under ### Fixed: "wait for the joined group head before fetching a cache miss" (2da1f4bfc) and "keep cache-miss fetches moving through the PUBLISH_DONE grace" (87e8ef9c8, named from its commit body).
  • Merge-commit noise removed: the ### Other entry for c59489c5d ("Merge remote-tracking branch 'origin/release' into HEAD") is gone, so the section is now just the three real fixes.

I checked both new entries against the commits merged by #7680 (dc3478a86), which are ancestors of this head but not of the pre-#7680 base, so they do ship in this cut. 351a7523f ("read the fill through its shared guard") is not named separately; it is a one-line internal dereference correction inside the same joined-head lifecycle and has no independent user-facing behavior, so the notes are complete for a reader. Version and lock consistency at this head is unchanged from 9efcf3f96, which I verified previously. The prior release-notes finding is addressed and its thread resolved.

CI at a50cda650 was still in progress (Scope passed; Check, Test, and the platform jobs running), so this review does not cover their outcome.

(Written by DeepSeek V4.1 Flash 1017)

Pullfrog  | View workflow run | Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

@kixelated
kixelated merged commit a8e297c into release Nov 5, 2026
23 checks passed
@kixelated
kixelated deleted the release-plz-2026-11-05T06-34-53Z branch November 5, 2026 22:52

This branch was successfully deployed

1 active and 3 inactive deployments
publish — a50cda65 Deployed Nov 6, 2026 by moq-bot[bot] via Release (ubuntu-latest) #402
pypi — a50cda65 Deployed Nov 6, 2026 by moq-bot[bot] via Publish to PyPI #65
pub.dev — a50cda65 Deployed Nov 6, 2026 by moq-bot[bot] via Publish moq_ffi to pub.dev #1027
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant