Skip to content

refactor(build): migrate construction and qualification to native Bazel - #295

Draft
f0rr0 wants to merge 150 commits into
mainfrom
f0rr0/native-bazel-release
Draft

f0rr0 wants to merge 150 commits into
mainfrom
f0rr0/native-bazel-release

Conversation

@f0rr0

@f0rr0 f0rr0 commented Oct 11, 2026 •

Copy link
Copy Markdown
Owner

Construction, affected CI and release selection currently infer ownership through separate paths. This migration makes configured Bazel targets declare their inputs, shipping files and required consumers. Release preparation compares qualified deliveries with authenticated completed publications; publication promotes those same qualified files.

  • Bazel owns construction and configured dependencies. CI verifies omitted work against an authenticated full baseline; structural changes or incomplete evidence require full qualification.
  • Conventional manifests retain independently versioned products and consumer requirements. Carriers inherit their owner's version. Release Please calculates versions and changelogs after delivery comparison selects necessary releases. A dependency edge alone does not force a bump.
  • Prepare reuses passing qualification for the exact source, or starts qualification and continues automatically after success. This takes effect after default-branch adoption.
  • Shared WASIX construction runs on Linux. Other hosts import its original files for native execution; Apple and Windows own their licensed SDK work. No remote executor is required.
  • Installed SDK, browser, Android and iOS consumers qualify actual shipping packages. Public dependency pins remain distinct from current workspace compilation, and final admission requires exact compatible artifacts.

The largest additions include generated dependency locks and offline Cargo registry snapshots. The final cutover removes the superseded Moon and legacy build/release machinery.

Validation remains in progress on 9210a675d4940b35d115509c483a9f4997b61b64.

  • Full Native qualification is running. Complete admission for all 27 products and device checks is pending.
  • The complete local release check passed: 1,027 main controller cases, the shell integration fixtures, metadata checks and independent-version checks. This includes actual held/current supplier synchronization and version-transition scenarios. All 15 Bazel source, formatting and lint targets passed.
  • GitHub transport tests exercise raw API response envelopes through the real pagination reader. A genuine completed Linux postmaster producer passed acquisition, archive validation, staging and source-bound consumer snapshot generation with no Bun on PATH; the wrapper uses the verified pinned runtime. Regression tests cover this actual shell path and empty-cache exclusion.
  • Local installed-package checks passed for the Node addon with all 32 contrib members and all seven external WASIX extensions. These exercise actual Cargo/npm carrier contents, activation, SQL, reopen, backup/restore and server use. The pg_textsearch archive matches the pinned upstream current installer and all 22 upgrade scripts.
  • The five Rust addon unit cases, owner Clippy checks and actual SDK payload File-identity regression passed. Hosted macOS, Windows and device execution remains governed by the current full run.

Before cutover, require this exact-source full Native run to pass, then acquire and review the genuine fourteen-slot seed-adoption anchor. Compose it with the reviewed legacy retirement and final cleanup, and pass one complete Native-only qualification of that combined source. Keep this PR draft until that final run passes. No version bump, merge or publication is included.

@vercel

vercel Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
oliphaunt-docs Ready Ready Preview Oct 19, 2026 8:04pm UTC

@f0rr0 f0rr0 changed the title build: establish native Bazel construction and qualification refactor(build): migrate construction and qualification to native Bazel Oct 11, 2026
Use the rules_swift compiler sandbox setting in manual Swift test adapters. Qualify the actual frozen SDK framework through its bundled installed consumer; current native production retains exact resource parity. Remove the duplicate SDK parity assertion and unused explicit-resource mode, which rejected authentic legacy archives stripped at different packaging stages.

This branch was successfully deployed

1 active deployment
Preview — 9210a675 Deployed Oct 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant