Repository navigation
chore: release - #5420
chore: release#5420
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 80721faa86
ℹ️ 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".
|
|
||
| - release | ||
|
|
||
| ## [0.19.25](https://github.com/moq-dev/moq/compare/moq-tokio-v0.19.24...moq-tokio-v0.19.25) - 2026-10-13 |
There was a problem hiding this comment.
Keep the 0.19.25 changelog entry unique
The parent already contains the 0.19.25 section immediately below, with the same comparison range and date. Adding a second heading makes the published release history report the same release twice and leaves tooling or readers unable to distinguish which section is authoritative. Merge the new bullet into the existing section, or use the actual next version if this represents another release.
Useful? React with 👍 / 👎.
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed 80721fa against base a5ff3fd.
No additional actionable correctness findings in the two-file diff. All 38 top-level Rust crate versions match Cargo.lock; internal version bumps are already in the base. The actual changes are three external dependency pins and the moq-tokio changelog, consistent with the configured dependency-update workflow.
The duplicate 0.19.25 changelog heading is already reported at #5420 (comment); referencing it rather than duplicating the comment. I did not establish a build or release-parser failure from it.
Static GitHub-only review; no builds or tests run. Upstream dependency behavior was not independently validated within this repository-only review.
c0b89f0 to
b512251
Compare
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: b512251 against 42ca851, comparing cumulatively with my review of 80721fa.
No new actionable bugs found. New external pins are tokio 1.53.2→1.53.3 and zerocopy/zerocopy-derive 0.8.62→0.8.63; their dependency lists and sources are unchanged. The 25 internal package bumps agree across manifests, applicable workspace requirements, lock entries and changelog headings; all 981 lockfile package references resolve unambiguously. The previously reported duplicate moq-tokio changelog heading is fixed.
The generated release-update direction is consistent. Source changes from #5430 and #5448 are inherited through the refreshed base, not new changes introduced by this release PR.
Verification: GitHub-only static review; no builds or runtime tests run, and upstream dependency behavior, registry contents and checksums were not independently validated.
b512251 to
340d9f8
Compare
340d9f8 to
b4b2c0e
Compare
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit: b4b2c0e, compared with the last published review at b512251, accounting for the updated release base.
No actionable bugs found in this update. Three new lockfile pins make this more than equivalent regeneration: equivalent 1.0.2 → 1.0.3, generator 0.8.10 → 0.8.11, and rustls 0.23.45 → 0.23.46. Their source/dependency lists are unchanged; all parsed lockfile dependency references resolve uniquely. Crate version bumps and workspace requirement changes remain identical to the previously reviewed release delta. Remaining changelog changes reflect dates/order and inherited base commits.
Direction: the generated release changes remain coherent. Rustls affects the TLS/QUIC stack, so locked build and interoperability coverage matter beyond metadata consistency.
Verification: GitHub-only static comparison of manifests, lockfile records and generated release changes. No builds or tests run, and no independent upstream implementation or registry-checksum audit.
|
Release check for head
(Written by Claude Opus 5.5) |
|
Auto-merge disabled: holding this until the backport of #5485 (hang: ignore incompatible archive metadata in catalogs) merges to (Written by Claude Opus 5.5) |
b4b2c0e to
1611538
Compare
|
Re-checked after the #5485 backport (#5520) landed. New head is
(Written by Claude Opus 5.5) |
🤖 New release
moq-net: 0.3.12 -> 0.3.13 (✓ API compatible changes)hang: 0.21.13 -> 0.21.14 (✓ API compatible changes)moq-mux: 0.10.13 -> 0.10.14 (✓ API compatible changes)moq-tokio: 0.19.25 -> 0.19.26 (✓ API compatible changes)moq-json: 0.5.10 -> 0.5.11moq-binary: 0.1.12 -> 0.1.13moq-loc: 0.2.21 -> 0.2.22moq-audio: 0.1.12 -> 0.1.13moq-video: 0.1.12 -> 0.1.13libmoq: 0.6.14 -> 0.6.15moq-archive: 0.0.13 -> 0.0.14moq-uring: 0.0.14 -> 0.0.15moq-boy: 0.5.14 -> 0.5.15moq-hls: 0.5.13 -> 0.5.14moq-stats: 0.2.14 -> 0.2.15moq-relay: 0.17.4 -> 0.17.5moq-rtc: 0.3.14 -> 0.3.15moq-rtmp: 0.3.13 -> 0.3.14moq-srt: 0.3.13 -> 0.3.14moq-transcode: 0.1.12 -> 0.1.13moq-cli: 0.14.4 -> 0.14.5moq-e2ee: 0.0.13 -> 0.0.14moq-ffi: 0.4.14 -> 0.4.15moq-gst: 0.4.14 -> 0.4.15moq-room: 0.2.13 -> 0.2.14Changelog
moq-nethangmoq-muxmoq-tokiomoq-jsonmoq-binarymoq-locmoq-audiomoq-videolibmoqmoq-archivemoq-uringmoq-boymoq-hlsmoq-statsmoq-relaymoq-rtcmoq-rtmpmoq-srtmoq-transcodemoq-climoq-e2eemoq-ffimoq-gstmoq-roomThis PR was generated with release-plz.
Need help on this PR? Tag
@codesmith-botwith what you need.