Skip to content

chore: release - #7750

Closed
moq-bot[bot] wants to merge 2 commits into
releasefrom
release-plz-2026-11-03T19-57-14Z
Closed

moq-bot[bot] wants to merge 2 commits into
releasefrom
release-plz-2026-11-03T19-57-14Z

Conversation

@moq-bot

@moq-bot moq-bot Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

🤖 New release

  • moq-net: 0.3.19 -> 0.3.20
  • moq-json: 0.5.17 -> 0.5.18
  • hang: 0.21.20 -> 0.21.21
  • moq-binary: 0.1.19 -> 0.1.20
  • moq-loc: 0.2.28 -> 0.2.29
  • moq-mux: 0.10.20 -> 0.10.21
  • moq-tokio: 0.19.32 -> 0.19.33
  • moq-audio: 0.1.19 -> 0.1.20
  • moq-video: 0.1.19 -> 0.1.20
  • libmoq: 0.6.21 -> 0.6.22
  • moq-archive: 0.0.20 -> 0.0.21
  • moq-auth: 0.2.3 -> 0.2.4
  • moq-uring: 0.0.21 -> 0.0.22
  • moq-boy: 0.5.21 -> 0.5.22
  • moq-hls: 0.5.20 -> 0.5.21
  • moq-stats: 0.2.21 -> 0.2.22
  • moq-relay: 0.17.11 -> 0.17.12
  • moq-rtc: 0.3.21 -> 0.3.22
  • moq-rtmp: 0.3.20 -> 0.3.21
  • moq-srt: 0.3.20 -> 0.3.21
  • moq-transcode: 0.1.19 -> 0.1.20
  • moq-cli: 0.14.11 -> 0.14.12
  • moq-e2ee: 0.0.20 -> 0.0.21
  • moq-ffi: 0.4.21 -> 0.4.22
  • moq-gst: 0.4.21 -> 0.4.22
  • moq-room: 0.2.20 -> 0.2.21
Changelog

moq-net

0.3.20 - 2026-11-03

Other

  • (net) backport session_fanout_threads to release
  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release
  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release

moq-json

0.5.18 - 2026-11-03

Other

  • updated the following local packages: moq-net

hang

0.21.21 - 2026-11-03

Other

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

moq-binary

0.1.20 - 2026-11-03

Other

  • updated the following local packages: moq-net

moq-loc

0.2.29 - 2026-11-03

Other

  • updated the following local packages: moq-net

moq-mux

0.10.21 - 2026-11-03

Other

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

moq-tokio

0.19.33 - 2026-11-03

Other

  • release

moq-audio

0.1.20 - 2026-11-03

Other

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

moq-video

0.1.20 - 2026-11-03

Other

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

libmoq

0.6.22 - 2026-11-03

Other

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

moq-archive

0.0.21 - 2026-11-03

Other

  • updated the following local packages: moq-net

moq-auth

0.2.4 - 2026-11-03

Other

  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release
  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release

moq-uring

0.0.22 - 2026-11-03

Fixed

  • require redacting web-transport-proto and redact moq-uring CONNECT Debug

Other

  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release

moq-boy

0.5.22 - 2026-11-03

Other

  • update Cargo.lock dependencies

moq-hls

0.5.21 - 2026-11-03

Other

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

moq-stats

0.2.22 - 2026-11-03

Other

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

moq-relay

0.17.12 - 2026-11-03

Other

  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release
  • Merge remote-tracking branch 'origin/release' into iter/log-secrets-release

moq-rtc

0.3.22 - 2026-11-03

Other

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

moq-rtmp

0.3.21 - 2026-11-03

Other

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

moq-srt

0.3.21 - 2026-11-03

Other

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

moq-transcode

0.1.20 - 2026-11-03

Other

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

moq-cli

0.14.12 - 2026-11-03

Other

  • update Cargo.lock dependencies

moq-e2ee

0.0.21 - 2026-11-03

Other

  • updated the following local packages: moq-net

moq-ffi

0.4.22 - 2026-11-03

Other

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

moq-gst

0.4.22 - 2026-11-03

Other

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

moq-room

0.2.21 - 2026-11-03

Other

  • updated the following local packages: moq-net, moq-auth, 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 head 88ccb8e against release base da09919.

No actionable release or dependency issue found in the actual diff, which only adds generated moq-tokio changelog text. The version changes listed in the PR description are already present on the base; this PR changes no manifests or lockfile.

Static GitHub-only review. I did not run release tooling, build, or publish; the Check and Release gate runs were still in progress during review.

@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 duplicate changelog section worth a look.

Reviewed changes

  • moq-tokio changelog: adds a - release bullet and a second ## [0.19.33] section dated 2026-11-03.
  • No manifest changes: the body advertises 25 bumps, but the only file in the diff is this changelog; Cargo.toml/Cargo.lock are untouched.

ℹ️ Release regenerates a version already on the base branch

The base (da09919e7, the merge of the previous release PR #7651) already carries every target version in the body, including moq-tokio 0.19.33, so this run looks stale rather than a new cut. Merging it would not bump any manifest and would only append a duplicate 0.19.33 heading to the changelog.

Technical details
# Stale release-plz run

## Affected sites
- `rs/moq-tokio/CHANGELOG.md:16` — second `## [0.19.33]` section for 2026-11-03.
- `rs/moq-tokio/Cargo.toml:8` — already `0.19.33` on the base branch; unchanged by this PR.

## Required outcome
- No duplicate `0.19.33` section in the changelog.
- If a new release is actually intended, the version must move past 0.19.33 (for example 0.19.34) instead of re-emitting the existing one.

## Open questions for the human
- Should this PR be closed and re-generated, given the base already has these versions?

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

Comment thread rs/moq-tokio/CHANGELOG.md Resolved
@pullfrog

pullfrog Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Correction to the inline suggestion in my review: that suggestion block was malformed and should be disregarded. The actual finding is that rs/moq-tokio/CHANGELOG.md now contains two identical ## [0.19.33] sections (this PR adds - release and then reopens the same version heading). Collapse them into one section, or bump past 0.19.33 if a new release is intended. No code change is proposed beyond that.

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

release-plz's release-pr ran before release published 0.19.33, so it
reopened the already-released section with a bogus "release" entry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@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

  • Removed the duplicate ## [0.19.33] section and the stray - release bullet from rs/moq-tokio/CHANGELOG.md, restoring the file to match release.

ℹ️ Branch is now content-identical to release

The tree at 79b635fe0 matches the base exactly (3c3892985), so the PR has no net file changes. Merging is a no-op; close it if no new release is intended.

Technical details
# No-op release PR

## Affected sites
- `rs/moq-tokio/CHANGELOG.md` — `79b635fe0` deletes the 6 lines added by `88ccb8e53`, so the file matches `release`.

## Required outcome
- None functionally. Decide whether to close this stale release-plz run or merge it as a harmless no-op.

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

@kixelated

Copy link
Copy Markdown
Collaborator

Closing: every bump listed here already shipped in #7651 (tags exist, and moq-tokio 0.19.33 is on crates.io). The only diff was a duplicate ## [0.19.33] heading in rs/moq-tokio/CHANGELOG.md, which I reverted, so this PR is empty. Likely cause: just rs release runs release-plz release-pr before release-plz release, so a release-PR run between the release merge and publishing reopens a release PR. That fix is being planned as a follow-up quest.

(Written by Claude Opus 5.5)

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