Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 36 additions & 3 deletions quest/m3/ffi-exporter.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,38 @@ dependency, so crates.io moq-ffi still builds (see the
workflows, `rs/moq-ffi/build.sh`, and `sh/` read the generators from it.
Delete `rs/uniffi-bindgen`, the "five places" comments in `flake.nix`, and the
`nix/uniffi-dart-*` lockfile and patch. The `sh/{kt,swift,dart,cpp}`
packaging scripts stay: they package moq.
packaging scripts stay, except the Swift FFI ones the release template below
replaces.
- **Python and Swift FFI releases** (maintainer, 2026-11-17, from
[kixel-ai/rust2#852](https://github.com/kixel-ai/rust2/pull/852), which added
rust2's [release template](https://github.com/kixel-ai/rust2/blob/main/ffi/release/README.md)):
moq-ffi's wheels and XCFramework come from rust2's shared `bindings.yml`
builder, published by the `release.yml` that
`package.py init --manifest-path rs/moq-ffi/Cargo.toml --swift-mirror moq-dev/moq-swift-ffi`
writes at the rust2 commit moq pins, plus `features: openh264`. It publishes
on the `moq-ffi-v*` tags moq already cuts. Register it as `moq-ffi`'s PyPI
trusted publisher in place of `release-py-ffi.yml`, then delete
`release-py-ffi.yml`, `release-swift-ffi.yml`,
`sh/swift/{package,verify,publish}-ffi.sh`, and the maturin section of
`pyproject.toml`. `release-swift-lib.yml`, `release-py.yml`, and
`sh/swift/{package,verify,publish}.sh` keep packaging the hand-written
wrappers, against the new FFI package.
- ✅ Floors rise to Python 3.11 (the stable ABI's first with the buffer
protocol), macOS 13 and Swift 6.2, with iOS 16 unchanged, and moq-ffi
ships no sdist, since a source build needs the nightly exporter
(rejected: keep Python 3.10; keep macOS 12.3 by gating `Swift.Duration`
APIs; a pre-exported sdist).
- ✅ Delete the Swift FFI packaging scripts the template replaces (rejected:
keep them), so one path packages the FFI.
- ✅ Accept the exporter's names: the Python import stays `moq_ffi`, the
Swift module becomes `MoqFfi` and the asset `MoqFfiFFI.xcframework.zip`
(today both `MoqFFI`), listed in `MIGRATE.md` (rejected: keep `MoqFFI`,
which needs a rename the exporter has no way to express).
- ✅ A new `swift-mirror` environment holds moq-bot's App credentials,
deployable only from `moq-ffi-v*` tags, so moq's `release.yml` stays
exactly what `package.py init` writes and a rust2 pin bump is a re-init
(rejected: hand-editing moq's copy to the existing `bot` environment;
renaming the template's environment in rust2 to moq's name).
- Zero-default durations (Decided 2026-11-03 (maintainer, follow-up planning after the 2026-11-03 /quest-afk and /quest-complete runs), from
[moq-dev/moq#7697](https://github.com/moq-dev/moq/pull/7697)): the
exporter gives generated duration fields a zero default, so a bare C++
Expand Down Expand Up @@ -149,8 +180,10 @@ they are.
Public API: breaking in every binding. moq-ffi's dependency names change,
generated C type names become CamelCase, the generated record
`MoqAudioEncoderFinished` becomes `MoqAudioEncoderFinish` in every language,
Dart's `MoqRoute.instanceId()` takes the exporter's name, and any other
generated name the wrappers re-export may change, each listed in the PR.
Dart's `MoqRoute.instanceId()` takes the exporter's name, the FFI Swift module
becomes `MoqFfi`, moq-ffi's floors rise to Python 3.11, macOS 13, and Swift
6.2 with no sdist, and any other generated name the wrappers re-export may
change, each listed in the PR.
Wire: none.

## Required
Expand Down