Repository navigation
chore: release - #7750
chore: release#7750moq-bot[bot] wants to merge 2 commits into
Conversation
kixelated
left a comment
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
ℹ️ No critical issues — one duplicate changelog section worth a look.
Reviewed changes
moq-tokiochangelog: adds a- releasebullet 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.lockare 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?deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏
|
Correction to the inline suggestion in my review: that suggestion block was malformed and should be disregarded. The actual finding is that
|
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>
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Removed the duplicate
## [0.19.33]section and the stray- releasebullet fromrs/moq-tokio/CHANGELOG.md, restoring the file to matchrelease.
ℹ️ 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.deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏
|
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 (Written by Claude Opus 5.5) |

🤖 New release
moq-net: 0.3.19 -> 0.3.20moq-json: 0.5.17 -> 0.5.18hang: 0.21.20 -> 0.21.21moq-binary: 0.1.19 -> 0.1.20moq-loc: 0.2.28 -> 0.2.29moq-mux: 0.10.20 -> 0.10.21moq-tokio: 0.19.32 -> 0.19.33moq-audio: 0.1.19 -> 0.1.20moq-video: 0.1.19 -> 0.1.20libmoq: 0.6.21 -> 0.6.22moq-archive: 0.0.20 -> 0.0.21moq-auth: 0.2.3 -> 0.2.4moq-uring: 0.0.21 -> 0.0.22moq-boy: 0.5.21 -> 0.5.22moq-hls: 0.5.20 -> 0.5.21moq-stats: 0.2.21 -> 0.2.22moq-relay: 0.17.11 -> 0.17.12moq-rtc: 0.3.21 -> 0.3.22moq-rtmp: 0.3.20 -> 0.3.21moq-srt: 0.3.20 -> 0.3.21moq-transcode: 0.1.19 -> 0.1.20moq-cli: 0.14.11 -> 0.14.12moq-e2ee: 0.0.20 -> 0.0.21moq-ffi: 0.4.21 -> 0.4.22moq-gst: 0.4.21 -> 0.4.22moq-room: 0.2.20 -> 0.2.21Changelog
moq-netmoq-jsonhangmoq-binarymoq-locmoq-muxmoq-tokiomoq-audiomoq-videolibmoqmoq-archivemoq-authmoq-uringmoq-boymoq-hlsmoq-statsmoq-relaymoq-rtcmoq-rtmpmoq-srtmoq-transcodemoq-climoq-e2eemoq-ffimoq-gstmoq-roomThis PR was generated with release-plz.