Skip to content

NimRTC v0.14.0

Choose a tag to compare

@github-actions github-actions released this 17 Oct 14:24
· 398 commits to main since this release

[0.14.0] - 2026-10-16

Status: Tech Preview

First pre-release of the v0.14.x cycle — the
v1.0.0-alpha.2 pre-release per docs/plan/v1.0-plan.md
§8 + §12.2 + §12.3.2. The marketing version stays anchored
to the v0.x line ("Tech Preview" banner unchanged from
v0.13.0); the NIMRTC_API_VERSION_PRE_RELEASE macro cycles
to "alpha.2". This is the seam land — no
WebTransportDataChannel impl exists yet; the existing
test_datachannel_engine 5/5 + test_sctp_usrsctp 4/4
regression surface continues to be the in-process validation.
The data-plane wire-up is the v0.14.0-beta.1 work per
docs/plan/v0.14-plan.md §2.1.2.

Tag cut: git tag -s v0.14.0 -m "v0.14.0 (alias: v1.0.0-alpha.2) — ...".
The tag message body documents the alias relationship to
v1.0.0-alpha.2 and the v0.x banner unchanged.

Tag day follow-ups (2026-10-16): the v0.14.0 tag was
force-re-pointed twice on tag day to fold in two release.yml
fixes that the tag-cut force-push surfaced:

  1. PR #20 (b5da037) — added -DNIMRTC_VENDORED_WEBRTC_APM=OFF
    to the four release.yml Configure steps so audio3a links
    against the same stub path that ci.yml uses, instead of
    chasing absl/base/config.h in the vendored WebRTC APM
    prebuild.
  2. dc15ad8 — added if: ${{ false }} to the four
    Prebuild WebRTC APM steps in release.yml (windows-msvc +
    linux-gcc + linux-aarch64 + macos-clang) so the meson /
    abseil-cpp subproject is no longer built before
    Configure. The long-term fix
    (target_link_libraries(audio3a PUBLIC webrtc_apm::webrtc_apm)
    so abseil's INCLUDE_DIRECTORIES propagate to the consumer) is
    tracked in a follow-up; until that lands, release.yml ships
    with the audio3a stub path, byte-equivalent to ci.yml.

RELEASING.md §2.3 tag immutability is preserved because the
v0.14.0 GitHub Release was a no-artefact draft at first cut
(release / publish was skipped / cancelled in
run #38898093864); no public announcement had been made. Each
re-point landed before the corresponding release / publish
re-run.

Highlights

  • WebTransport / QUIC vendor decision (ADR-014) —
    docs/adr/ADR-014-web-transport-vendor.md (Status:
    Accepted). msquic chosen as the WebTransport / QUIC backend
    for the v0.14.0-beta.1 WebTransportMsQuicSession impl. The
    5 evaluation criteria in v1.0-plan.md §10.2 (license /
    no-Rust / no-CFFI / cross-platform CI / Windows-first /
    active maintenance) are verified by the spike at
    interop/v0_14_msquic_spike/; results.txt records
    per-criterion PASS/FAIL with timestamps + commit SHAs.
    License (MIT), no Rust / no CFFI, cross-platform CI green
    (windows-2022 + linux-gcc + macos-clang + linux-aarch64),
    Windows-first (kernel QUIC), active maintenance (last commit
    within 6 months of v0.14.0 tag cut). Fallback to quiche
    (BSD-2, C API, userspace only on Windows) is documented in
    ADR-014 §Alternatives + §Consequences.

  • IWebTransportSession interface — pure-virtual seam
    (no impl) at
    src/web_transport/include/nimrtc/web_transport/web_transport_session_iface.hpp.
    Companion headers:

    • bidi_stream_iface.hpp — IBidirectionalStream
    • uni_stream_iface.hpp — IUnidirectionalStream
    • datagram_facade.hpp — DatagramFacade (utility wrapper)
    • web_transport_config.hpp — WebTransportConfig
      (max_idle_timeout_ms / initial_max_stream_data /
      initial_max_data / keep_alive_interval_ms)
    • web_transport_state.hpp — WebTransportState enum
      (kConnecting / kConnected / kClosing / kClosed / kFailed)
    • web_transport_session_factory.hpp —
      IWebTransportSessionFactory (the typed factory
      contract)
      All seven headers are NIMRTC_API_UNSTABLE (the
      classification is visual at v1.0.0-alpha.2; the "v1.0.0
      stable" banner does not flip until v1.0.0 final).
  • core::PluginRegistry::register_web_transport() slot —
    parallel to the Slice 8 DTLS / SCTP / raw_udp /
    transport-stack slots. The factory slot exists at the
    alpha.2 cut; the msquic factory lands in beta.1 alongside
    the msquic integration. list_web_transports() returns an
    empty vector at the alpha.2 cut; user-supplied factory ids
    resolve normally, and unknown ids return nullptr (no silent
    fallback to wolfSSL). Two new subtests in
    test_engine_plugin_loading.cpp:

    • wt014_registry_slot_is_typed_for_web_transport_factory
    • wt014_registry_default_registrars_omits_web_transport_until_beta1
  • Compile-only seam test —
    tests/test_web_transport_seam.cpp (new). Verifies every
    pure-virtual interface is std::is_abstract, every
    WebTransportConfig default matches the v1.0-plan.md
    §10.4 contract (RFC 9000 / RFC 9221), and every
    WebTransportState enum value round-trips. 5 subtests
    PASS on Windows MSVC. No msquic link required (the seam is
    vendor-agnostic; the impl lands in beta.1).

  • v0.14.x spike-validation program — 6 spike programs at
    interop/v0_14_msquic_spike/ exercise the full msquic C
    API surface against the planned IWebTransportSession
    methods:

    • echo_client.cpp / echo_server.cpp — 0-RTT echo
      round-trip latency < 50 ms
    • stream_reset.cpp — MsQuicStreamSendComplete + reset
    • datagram_roundtrip.cpp — MsQuicDatagramSend / recv
    • concurrent_streams.cpp — 16-stream fanout
      The results.txt file is the gating evidence for ADR-014's
      criterion 5 ("active maintenance"); per-criterion PASS/FAIL
      with timestamps + commit SHAs.

Added

  • src/web_transport/include/nimrtc/web_transport/*.hpp
    (7 new public headers) — the WebTransport / QUIC seam.
    All headers are NIMRTC_API_UNSTABLE (the v1.0.0-alpha.2
    classification; stable banner does not flip until v1.0.0
    final).

  • IWebTransportSession interface in
    web_transport_session_iface.hpp. Methods: state(),
    open_bidi_stream(), open_uni_stream(),
    send_datagram(), set_on_datagram(), close(). Pure
    virtual; no impl.

  • IBidirectionalStream + IUnidirectionalStream
    interfaces in bidi_stream_iface.hpp /
    uni_stream_iface.hpp. Bidi methods: send / recv /
    set_on_data / close / reset. Uni methods: send /
    close / reset.

  • WebTransportConfig in web_transport_config.hpp —
    small struct mirroring the QUIC settings the msquic
    backend exposes through QUIC_SETTINGS + QUIC_CONFIGURATION
    parameters. Defaults match RFC 9000 / RFC 9221.

  • WebTransportState enum in
    web_transport_state.hpp — 5-value enum
    (kConnecting / kConnected / kClosing / kClosed /
    kFailed) with uint8_t underlying type.

  • DatagramFacade in datagram_facade.hpp — non-virtual
    utility wrapper around IWebTransportSession's datagram
    surface. Binds a non-owning pointer to the session; the
    facade does not extend the session's lifetime.

  • IWebTransportSessionFactory in
    web_transport_session_factory.hpp — typed factory
    contract; matches the dtls::IDtlsSessionFactory /
    sctp::ISctpSocketFactory / raw_udp::IRawUdpFactory /
    ITransportStackFactory pattern. No factory is
    auto-registered at the alpha.2 cut; the msquic factory
    lands in beta.1.

  • NIMRTC_REGISTER_WEB_TRANSPORT macro in
    src/core/include/nimrtc/core/registry.hpp —
    static ::nimrtc::core::detail::Registrar wrapper for the
    new typed slot, parallel to the existing
    NIMRTC_REGISTER_DTLS_SESSION / SCTP_SOCKET /
    RAW_UDP_DATAGRAM / TRANSPORT_STACK macros.

  • core::PluginRegistry::register_web_transport(id, factory*) / get_web_transport(id) /
    list_web_transports()
    — new typed slot on
    core::PluginRegistry. Forward-declared in registry.hpp;
    no msquic headers leak into core (Layout Invariant 1
    preserved).

  • tests/test_web_transport_seam.cpp (new, 5 subtests):
    seam_interfaces_are_abstract /
    datagram_facade_forwards_to_session /
    datagram_facade_with_null_session /
    callbacks_accept_lambdas /
    state_enum_round_trip. Compile-only test; the gate is
    "the seam headers compile + link on all 4 platforms".

  • 2 new EnginePluginLoading subtests in
    tests/test_engine_plugin_loading.cpp:

    • wt014_registry_slot_is_typed_for_web_transport_factory —
      verifies the slot exists, accepts a user-registered
      factory, and resolves by id.
    • wt014_registry_default_registrars_omits_web_transport_until_beta1 —
      pins the alpha.2 → beta.1 transition: no factory is
      auto-registered at the alpha.2 cut; the msquic factory
      lands in beta.1.
  • NIMRTC_API_VERSION_PRE_RELEASE cycles to "alpha.2"
    in src/core/include/nimrtc/core/api_version.hpp.

  • interop/v0_14_msquic_spike/ (new) — spike-validation
    program for ADR-014. README.md documents the 5-criterion
    check; results.txt records per-criterion PASS/FAIL with
    timestamps + commit SHAs. 6 spike programs exercise the
    full msquic C API surface against the planned
    IWebTransportSession methods. No msquic source code
    lands in v0.14.0 alpha.2 (the integration lands in beta.1).

  • docs/adr/ADR-014-web-transport-vendor.md (new) —
    msquic vendor decision. 5 evaluation criteria in
    v1.0-plan.md §10.2 verified by the spike at
    interop/v0_14_msquic_spike/. Fallback to quiche
    documented in §Alternatives + §Consequences.

Changed

  • src/core/include/nimrtc/core/registry.hpp — adds the
    register_web_transport / get_web_transport /
    list_web_transports methods (parallel to the Slice 8
    DTLS / SCTP / raw_udp / transport-stack slots), the
    NIMRTC_REGISTER_WEB_TRANSPORT macro, the kWebTransport
    Category enum entry, and the matching case in
    Registrar::Registrar. Forward-declares
    nimrtc::web_transport::IWebTransportSessionFactory so
    the registry's TypedRegistry<...> field and public
    method signatures can reference the factory type without
    pulling the seam headers into core (Layout Invariant 1
    preserved).

  • tests/CMakeLists.txt — adds the
    nimrtc_add_web_transport_seam_test() function and the
    test_web_transport_seam target registration. The
    function follows the nimrtc_add_core_api_test() pattern
    (links nimrtc::core + GTest; no msquic dependency).

  • src/core/include/nimrtc/core/api_version.hpp —
    NIMRTC_API_VERSION_PRE_RELEASE cycles from "alpha.1"
    to "alpha.2". The matching
    nimrtc::core::api_version::kPreRelease constant is
    updated automatically (the macro is the source of truth).

  • CHANGELOG.md — [1.0.0-alpha.2] section finalised;
    [1.0.0-beta.1] placeholder added; [Unreleased] reset
    to a minimal pointer to v0.14-plan.md.

Notes

  • Public API surface diff vs v0.13.0: additive only.

    • New headers:
      src/web_transport/include/nimrtc/web_transport/*.hpp
      (7 new public headers — the seam + factory + companions).
    • New registry methods:
      core::PluginRegistry::register_web_transport() /
      get_web_transport() / list_web_transports().
    • New macro: NIMRTC_REGISTER_WEB_TRANSPORT(id, factory_ptr).
    • No existing public symbol is modified or removed.
    • No existing public symbol is marked DEPRECATED in
      v0.14.0
      (the deprecation policy in ADR-015 §Decision 3
      governs; the first NIMRTC_API_DEPRECATED annotations on
      existing public symbols are reserved for the
      v1.0.0-beta.1 → v1.0.0-rc.1 window where the public API
      surface starts the additive-only freeze per
      v1.0-plan.md §12.2 v1.0.0-beta.1 Gate #5).
  • ABI: experimental through v1.0.0. Pin to a specific
    commit. The new seam headers are NIMRTC_API_UNSTABLE; the
    classification is visual at the alpha.2 cut
    (NIMRTC_API_UNSTABLE expands to nothing in default
    mode).

  • Data plane: still SCTP-over-DTLS at the alpha.2 cut
    (the existing test_datachannel_engine 5/5 +
    test_sctp_usrsctp 4/4 regression surface continues).
    WebTransport / QUIC impl lands in v0.14.0-beta.1.

  • 4-platform CI: green on windows-2022 + linux-gcc +
    macos-clang. linux-aarch64 may be TEMP-DISABLED per
    v0.12.0 baseline; if so, the release notes record the
    reason.

  • usrsctp 0.9.5.0 still in tree (v1.2.0 removal per
    v1.0-plan.md §2.2).

  • No new third-party dependencies for the default
    (non-msquic) build. The msquic integration is
    NIMRTC_ENABLE_WEB_TRANSPORT_MSQUIC=ON opt-in (default
    ON at the beta.1 cut; the seam headers compile without
    it).

What is NOT in v0.14.0 (deferred to v0.14.0-beta.1 or later)

  • WebTransport / QUIC impl (msquic integration) —
    v0.14.0-beta.1. The src/third_party/msquic/ git
    submodule + cmake/FindMsQuic.cmake + the
    WebTransportMsQuicSession + WebTransportMsQuicSessionFactory
    (id = "msquic") all land in beta.1.
  • WebTransportDataChannel impl — v0.14.0-beta.1.
  • Chrome e2e Case E — v0.14.0-beta.1.
  • EngineConfig::datachannel_backend field —
    v0.14.0-beta.1.
  • L1 strict-priority scheduling across the DC plane
    (DC-2)
    — v1.0.0-beta.2 (per v1.0-plan.md §8 + §12.3.4).
  • SFU-1 / DC-3 / BENCH-1 — pre-1.0 decision window per
    v1.0-plan.md §7.
  • usrsctp src/third_party/usrsctp/ removal — v1.2.0
    (per v0.11-plan.md §2.2 + v1.0-plan.md §2.2).
  • DTLS 1.3 re-enablement on wolfSSL 5.9.2+ — v1.x
    (per v1.0-plan.md §2.2 + docs/plan/dtls_chrome_interop_review.md).
  • max_p99_ms budget enforcement — slipped to v0.14.x
    or v0.15.x if not landed in v0.14.0.
  • OHAudio HAL adapter implementation — slipped to
    v0.14.x or v0.15.x if not landed in v0.14.0.
  • cross-network-peer naming review — slipped to
    v0.14.x if not landed in v0.14.0.
  • §5.3 rule 2 media-plane production hardening (FEC +
    codec + ARQ reliability)
    — v0.14.x slip-or-land or
    later.
  • Composite sfu-agent Profile resolution — pre-1.0
    decision window.
  • Adaptive JitterBuffer + Goog-CC full mainline BWE —
    v1.x.
  • GM/T 国密 SRTP backend — v1.x.
  • AddressSanitizer CI matrix — v1.x.
  • Per-symbol inline stability annotation — v0.14.x
    slip-or-land (the v0.13.0 sweep was at the file level;
    the per-symbol pass is a v0.14.x follow-up).

⚠️ This is an UNSIGNED pre-1.0 Tech Preview release.
The release assets are published without detached GPG
signatures because the GPG_PRIVATE_KEY / GPG_FINGERPRINT
secrets are not configured in this repository.
Verify integrity using the per-platform .sha256 files only.
Signed releases resume with v1.0.0 (see RELEASING.md §3.3).