chore: release - #4320
chore: release#4320moq-bot[bot] wants to merge 1 commit into
Conversation
|
RECONSIDER — do not merge this release-plz PR. This looks like a broken second release-plz run right after #4256 merged (that real release landed at 23:04 UTC; this PR opened at 23:09 UTC). Why this is not a positive improvement
Complexity / better approach
This is an automated review, not the maintainer's decision |
There was a problem hiding this comment.
💡 Codex Review
Line 10 in 6f82585
The parent release commit already contains the complete 0.19.19 section, including the same comparison URL and date. Adding it again makes the changelog list one published version twice with overlapping but different contents, so consumers cannot tell which notes belong to the actual release. Keep the existing section and add the release entry to it instead.
ℹ️ 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".
e16f0d3 to
7a84ed8
Compare
d52fe0d to
3faff04
Compare
11f53f4 to
36e10ec
Compare
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed commit 36e10ec.
Direction: the coordinated release metadata update is appropriate. Prefer keeping unrelated dependency refreshes separate when practical, so release validation is attributable to a smaller change; the lockfile also advances iroh and other external packages.
No confirmed release-metadata defect in the refreshed diff. The old duplicate moq-tokio 0.19.19 concern is no longer present: this head adds a 0.19.20 section before the existing 0.19.19 section.
Verification: static diff and targeted source inspection. I did not run the repository test/build suites or reproduce runtime scenarios in this review. This is a COMMENT review, not a merge approval.
5c9d66a to
bdbb14b
Compare
bdbb14b to
dad40aa
Compare
🤖 New release
kio: 0.6.1 -> 0.6.2 (✓ API compatible changes)moq-pattern: 0.1.1 -> 0.1.2 (✓ API compatible changes)moq-net: 0.3.7 -> 0.3.8 (✓ API compatible changes)moq-json: 0.5.5 -> 0.5.6 (✓ API compatible changes)moq-mux: 0.10.8 -> 0.10.9 (✓ API compatible changes)moq-sock: 0.1.0 -> 0.2.0 (⚠ API breaking changes)moq-tokio: 0.19.19 -> 0.19.20 (✓ API compatible changes)moq-audio: 0.1.7 -> 0.1.8 (✓ API compatible changes)moq-video: 0.1.7 -> 0.1.8 (✓ API compatible changes)libmoq: 0.6.8 -> 0.6.9moq-auth: 0.1.5 -> 0.2.0 (✓ API compatible changes)moq-uring: 0.0.9 -> 0.0.10 (✓ API compatible changes)moq-boy: 0.5.8 -> 0.5.9moq-hls: 0.5.8 -> 0.5.9 (✓ API compatible changes)moq-relay: 0.15.8 -> 0.16.0 (✓ API compatible changes)moq-rtc: 0.3.8 -> 0.3.9 (✓ API compatible changes)moq-rtmp: 0.3.8 -> 0.3.9 (✓ API compatible changes)moq-srt: 0.3.8 -> 0.3.9 (✓ API compatible changes)moq-cli: 0.12.8 -> 0.13.0moq-ffi: 0.4.8 -> 0.4.9moq-gst: 0.4.8 -> 0.4.9 (✓ API compatible changes)hang: 0.21.8 -> 0.21.9moq-binary: 0.1.7 -> 0.1.8moq-loc: 0.2.16 -> 0.2.17moq-archive: 0.0.8 -> 0.0.9moq-stats: 0.2.8 -> 0.2.9moq-transcode: 0.1.7 -> 0.1.8moq-e2ee: 0.0.8 -> 0.0.9moq-room: 0.2.8 -> 0.2.9⚠
moq-sockbreaking changesChangelog
kiomoq-patternmoq-netmoq-jsonmoq-muxmoq-sockmoq-tokiomoq-audiomoq-videolibmoqmoq-authmoq-uringmoq-boymoq-hlsmoq-relaymoq-rtcmoq-rtmpmoq-srtmoq-climoq-ffimoq-gsthangmoq-binarymoq-locmoq-archivemoq-statsmoq-transcodemoq-e2eemoq-roomThis PR was generated with release-plz.