diff --git a/quest/m1/README.md b/quest/m1/README.md index bbf5a6796dc..cb208bf0199 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -124,7 +124,6 @@ lite-07 stream type here. - [lite-06 max sequence](/quest/m1/lite06-max-sequence.md) - group sequence 2^62-1 reaches a lite-06 subscriber or is refused loudly, instead of vanishing - [Track live signal](/quest/m1/track-live.md) - a reader can wait for its track's feed to be live, so a player skips old cached groups while a fresh upstream subscription starts -- [C++ and OBS package proof](/quest/m1/cpp-package-check.md) - the installed artifacts pass before their first release - [Binding check cost](/quest/m1/binding-check-cost.md) - `moq.cpp` compiles once per C++ standard and Gradle stays warm, measured before and after - [Audio devices on ARM](/quest/m1/audio-devices-arm.md) - `just rs audio-devices` passes on the hosted ARM runner - [CI housekeeping](/quest/m1/ci-housekeeping.md) - queue nextest at 24 threads, stale Pages artifacts cleared, the actionlint ignore dropped diff --git a/quest/m1/cpp-package-check.md b/quest/m1/cpp-package-check.md deleted file mode 100644 index 9fbd97b2aa0..00000000000 --- a/quest/m1/cpp-package-check.md +++ /dev/null @@ -1,33 +0,0 @@ -# [XS] C++ and OBS packages pass their nightly dry run - -## Goal - -The release C++ archives and matching OBS plugin build and run their package -checks before the first tag, using locally built release artifacts. - -## Plan - -Extracted from first C++ publication on 2026-10-13 to avoid waiting for a tag -before validating its build path. Keep publication tag-only. The first -publication and released-download proof stay in release execution. - -[#6006](https://github.com/moq-dev/moq/pull/6006) landed the build path: each -packaged archive runs the installed-consumer checks (`just cpp check ---archive`), and an OBS dry run links the matching checked archive -(`just obs package --moq-archive`, CMake `MOQ_ARCHIVE_FILE`) instead of a -release download. It passed on one Linux host locally. - -What remains is the proof from a scheduled Nightly on `main` after #6006: - -- Its `Release Cpp` job (`.github/workflows/release-cpp.yml` through - `nightly.yml`) builds and checks the C++ archive for all four targets, and - packages the OBS plugin against the checked archive for the two OBS - targets, macOS and Windows. Linux OBS is build-from-source and ships no - plugin. -- Its separate Linux `OBS` lane (`just obs ci`) passes the settings and - session-report tests. That lane builds the plugin in-tree, not from the - packaged archive. - -Fix whatever those runs turn up; delete this quest once both are green. - -Public API: none beyond the binding changes owned by their quests. Wire: none. diff --git a/quest/m2/cpp-ffi-reuse.md b/quest/m2/cpp-ffi-reuse.md index 70413cd2342..76676a14b48 100644 --- a/quest/m2/cpp-ffi-reuse.md +++ b/quest/m2/cpp-ffi-reuse.md @@ -59,5 +59,4 @@ the default FFI build across Go, Kotlin and Swift. ## Related -- [C++ and OBS package proof](/quest/m1/cpp-package-check.md) - the installed-consumer checks this reuses - [First shared FFI release](/quest/m0/ci/nightly-ffi-reuse.md) - confirms the shared build in production first diff --git a/quest/m2/release/cpp-release.md b/quest/m2/release/cpp-release.md index ffb5f30fb83..7f5e5804ecd 100644 --- a/quest/m2/release/cpp-release.md +++ b/quest/m2/release/cpp-release.md @@ -20,16 +20,21 @@ last moq-c build until this tag. Decided when the C++ line landed on `main` Advanced settings or the dock's protocol and reconnect reason that the moq-c build had, so those parity quests gate this release. -The [nightly package proof](/quest/m1/cpp-package-check.md) owns pre-cut -preparation. This quest owns tagging and verifying the published downloads. +The nightly C++ and OBS release checks pass: the +[2026-10-20 Nightly](https://github.com/moq-dev/moq/actions/runs/39421743227), +which failed only in unrelated lanes, checked the installed consumers of all four packaged archives and built both +OBS plugins against them. It packages this run's prebuilt moq-ffi input, +while a tag with `cpp/moq/FFI_VERSION` unset builds moq-ffi from source, a +path no nightly checks. So if the pin is still unset, first dispatch +`release-cpp.yml` on the ref to be tagged without `prebuilt-test`: it runs +the tag's source build and archive check on all four hosts, then both OBS +builds, and publishes nothing. This quest owns that dry run, tagging, and verifying the +published downloads. Decided in the 2026-10-10 audit: the tag also waits for Codecs and the epoch rename, so consumers take the binding breaks in one -release. The nightly dry-run preparation can proceed independently. +release. ## Required - [Breaking release cut](/quest/m2/release/cut.md) - prepared code reaches release before artifact publication and installed proof - - -- [Nightly package proof](/quest/m1/cpp-package-check.md) - the release path is exercised before the tag