[kixelated]

Republishes moq-gst so that a moq-gst-v* tag runs moq-gst.yml again, now with moq-dev/moq#8109's sandbox-safe Homebrew formula test.

0.4.21 to 0.4.23 reached crates.io, but their GitHub releases never published. The Build tarball (aarch64-apple-darwin) job hung in brew test. This bump changes no code. Once it merges, release-plz publishes 0.4.24 and pushes moq-gst-v0.4.24. That tag's run checks the fix for quest/m0/ci/gst-release-macos.md, carried by moq-dev/moq#8105.

The maintainer picked a patch bump in /quest-unblock on 2026-11-07.

Public API: none. Wire: none.

Review

Skipped local review at d3fbfe9c7e: version-only bump (Cargo.toml, Cargo.lock, CHANGELOG), no code changes; head contains current origin/release.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[kixelated]

Automated review by review (OpenAI)

Reviewed commit: d3fbfe9
Base: bbecb46

No actionable findings in the three-file version bump. Cargo.toml and Cargo.lock both move moq-gst from 0.4.23 to 0.4.24, and the changelog describes the republish rather than claiming a plugin code fix. This targets release, whose Release RS workflow includes these paths and whose moq-gst tag workflow publishes only after packaging succeeds. The head includes #8109's sandbox-safe formula test; the separate out-of-sandbox GStreamer smoke test remains enabled.

Direction: the patch bump is consistent with retriggering the release pipeline. Completion still depends on the new tag's builds and publication succeeding.

Verification: GitHub-only static inspection of the diff, release configuration/workflows, and Homebrew test/template. I did not build or publish the package, run Homebrew, or verify a future release/tag. No credentials or publication settings were changed.

This is a COMMENT, not an approval or merge-readiness certification.

(Written by review (OpenAI))

[pullfrog]

✅ No new issues found.

Reviewed changes

The moq-gst 0.4.24 release cut on release, three files:

• rs/moq-gst/Cargo.toml — version 0.4.23 to 0.4.24.
• Cargo.lock — the matching moq-gst lockfile entry.
• rs/moq-gst/CHANGELOG.md — a hand-written 0.4.24 section recording the republish and citing #8109.

No code, public API, or wire changes.

I verified the mechanics the PR depends on:

• .release-plz.toml disables only git_release_enable; git_tag_enable stays at its default, so release-plz release on the release push publishes 0.4.24 and pushes moq-gst-v0.4.24, and that tag's moq-gst.yml run creates the GitHub release itself. The PR body's description matches the workflow.
• crates.io's max moq-gst version is still 0.4.23 and no moq-gst-v0.4.24 tag exists, so the publish will not collide.
• The claim that 0.4.21 through 0.4.23 never got GitHub releases holds: the newest moq-gst-v* release is 0.4.20.
• The fix this republish tests is on release: base bbecb46a5 (#8109) makes .github/homebrew/Formula/moq-gst.rb.tmpl identical to main's sandbox-safe version, and release-brew only runs after a successful tag workflow, so the tap stayed on 0.4.20 rather than pointing at missing assets.
• No other file in the workspace pins the moq-gst version.

The only inherent risk is that this publish is also the live test of the formula fix: if the tag run still fails, 0.4.24 is spent on crates.io and the next attempt needs 0.4.25. The PR body and quest/m0/ci/gst-release-macos.md already record that tradeoff, so nothing to change.

  ^{｜ View workflow run ｜ Using deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) ｜ 𝕏}