Repository navigation
chore: release - #7009
chore: release#7009moq-bot[bot] wants to merge 3 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0eacd42c8b
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
kixelated
left a comment
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: 0eacd42
The actual diff only adds ten lines to rs/moq-tokio/CHANGELOG.md; it does not change crate versions, dependencies, lockfiles, or runtime code, despite the release summary. I confirmed the duplicate 0.19.30 heading at line 20 already reported in the existing finding, so I am not adding a duplicate inline comment. Keep one version section rather than introducing a second identical release entry. No additional actionable bugs found.
Overall direction: this is redundant release-note generation, not a new version update; consolidating the existing entry is the simpler result. Verification was static inspection of the complete diff and surrounding changelog; no tests, builds, or release dry run were executed.
0eacd42 to
15ff424
Compare
kixelated
left a comment
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: 15ff424
No new actionable bugs found in the updated release diff. Compared with my previous review, this is now a real 25-crate patch release: crate versions, workspace dependency requirements, and lockfile package versions agree. I separated changes already on the updated release base from this PR's changes.
Fixed: the previous duplicate 0.19.30 changelog finding is absent from the current tree; rs/moq-tokio/CHANGELOG.md:10–20 contains one 0.19.31 section followed by one 0.19.30 section.
Direction: coordinated version/changelog updates are appropriate and add no runtime complexity. The additional aws-lc-rs 1.18.2 → 1.19.0 / aws-lc-sys 0.46.0 → 0.47.0 lockfile refresh is a distinct dependency change; keeping it separate would make the release-only diff easier to audit.
Verification: static inspection of the complete current PR patch, commit comparisons, workspace constraints, and surrounding changelog. No builds, tests, upstream cryptography audit, or release dry run were executed.
15ff424 to
2eea601
Compare
kixelated
left a comment
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed 2eea60184f53ed7b5fa9b38642fee868d2bb876f against the last published review at 15ff4240727474edc445a6c7a4a8ad46c9107334, accounting for the updated release base 6da7efd0d8f31dcb8741674abfa7a8736544a269.
No new actionable findings. The 25 crate-version changes remain consistent with workspace requirements, lock entries, and changelog headings. The earlier duplicate moq-tokio release heading remains fixed. The Opus implementation change is already on the base, not introduced by this release PR.
The meaningful dependency delta since the previous review is ctutils 0.4.7, utf8_iter 1.1.0 with utf_types 1.0.0, and zcheapstr 1.2.0; the AWS-LC refresh was already reviewed. Direction: coordinated release metadata remains appropriate. Keeping unrelated dependency refreshes separate would make this release easier to audit, but no concrete consumer regression was established here.
Verification limits: GitHub-only static inspection with an independent consistency check. No builds, tests, dependency-source audit, MSRV verification, or release dry run were performed.
(Written by OpenAI)
|
Landing the Rust patch release. It now includes the Opus edit backport moq-dev/moq#7273 ( (Written by Claude Opus 5.5) |
🤖 New release
moq-net: 0.3.17 -> 0.3.18 (✓ API compatible changes)moq-mux: 0.10.18 -> 0.10.19 (✓ API compatible changes)moq-tokio: 0.19.30 -> 0.19.31 (✓ API compatible changes)moq-relay: 0.17.9 -> 0.17.10 (✓ API compatible changes)moq-json: 0.5.15 -> 0.5.16hang: 0.21.18 -> 0.21.19moq-binary: 0.1.17 -> 0.1.18moq-loc: 0.2.26 -> 0.2.27moq-audio: 0.1.17 -> 0.1.18moq-video: 0.1.17 -> 0.1.18libmoq: 0.6.19 -> 0.6.20moq-archive: 0.0.18 -> 0.0.19moq-uring: 0.0.19 -> 0.0.20moq-boy: 0.5.19 -> 0.5.20moq-hls: 0.5.18 -> 0.5.19moq-stats: 0.2.19 -> 0.2.20moq-rtc: 0.3.19 -> 0.3.20moq-rtmp: 0.3.18 -> 0.3.19moq-srt: 0.3.18 -> 0.3.19moq-transcode: 0.1.17 -> 0.1.18moq-cli: 0.14.9 -> 0.14.10moq-e2ee: 0.0.18 -> 0.0.19moq-ffi: 0.4.19 -> 0.4.20moq-gst: 0.4.19 -> 0.4.20moq-room: 0.2.18 -> 0.2.19Changelog
moq-netmoq-muxmoq-tokiomoq-relaymoq-jsonhangmoq-binarymoq-locmoq-audiomoq-videolibmoqmoq-archivemoq-uringmoq-boymoq-hlsmoq-statsmoq-rtcmoq-rtmpmoq-srtmoq-transcodemoq-climoq-e2eemoq-ffimoq-gstmoq-roomThis PR was generated with release-plz.
Review
Codex (
quest review), gpt-6.1-sol, medium effort, head 2eea601 againstreleasede0a2b0: no findings. Head 0cee315 adds only conflict-free merges ofrelease(de0a2b0, the@moq/publish0.5.4 bump, and 2695195, the bot key moved into protected environments), which the guide exempts from a new review. The earlier Codex finding (a duplicate moq-tokio 0.19.30 heading) is fixed by the refresh and its thread is resolved.(Written by Claude Opus 5.5)