Release Manifest
Release Manifest
Source builds are active today. Public installers, signing, and verification artifacts are still being prepared.
# RELEASE_01
〈MACOS〉
/CHANNEL: PUBLIC
- ARCH:
- AARCH64 / X86_64
- SIGNING:
- IN PREPARATION
- SIZE:
- 45.2 MB
- CHECKSUM:
- Available with public release artifacts
STATUS: ACTIVE
# RELEASE_01
〈WINDOWS〉
/CHANNEL: PUBLIC
- ARCH:
- X86_64
- SIGNING:
- IN PREPARATION
- SIZE:
- -
- CHECKSUM:
- -
STATUS: PREPARING
STATUS: RELEASE PREPARATION
# RELEASE_01
〈LINUX〉
/CHANNEL: PUBLIC
- ARCH:
- X86_64
- SIGNING:
- IN PREPARATION
- SIZE:
- -
- CHECKSUM:
- -
STATUS: PREPARING
STATUS: RELEASE PREPARATION
Telemetry Is Compile-Gated in Land.
Telemetry and tracing are behind named Rust feature gates in the native layer. Nothing is emitted by default. Each build profile explicitly lists which paths are compiled in.
Telemetry Policy
Full disclosure on what Land collects - and what it does not.
Compile-gated by default.
Telemetry and tracing code lives behind
cfg(feature)gates. In a standard build those paths are not compiled in - no collection, no emission, no runtime cost.
No Microsoft endpoint dependency.
Land is built from a CC0 Code-OSS base with Microsoft service dependencies removed or replaced. The crash reporter, update service, and marketplace endpoints are all replaced with Land-owned wiring or left unconnected.
Three separate systems, three separate controls.
Website analytics, account authentication, and editor telemetry are independent systems. Each is controlled by its own feature flag or environment configuration - none of the three implies the others are active.
Disabled feature paths stay out of the runtime.
Rust
cfg(feature)gates eliminate disabled code paths at compile time, not just at runtime. A published build profile is a verifiable record of exactly which features were included.Need traces? Opt in. Your infrastructure only.
OpenTelemetry tracing is available in source and activates only when a deployment explicitly enables it with a named feature flag and a configured endpoint. Trace data goes to your infrastructure.
cargo build --features TelemetrySub-features: MetricsCollection,DistributedTracing
Extension host timing stays in the process.
Cocoon has internal timing and service diagnostics for extension-host work. Unless a transport is configured, that data is local process instrumentation rather than an external product-analytics claim.
Build Variants
9 named profiles across 16 test permutations. Every combination verified.
| Profile | Tier | Workbench | Features | Status |
|---|---|---|---|---|
| debug | Browser | Browser UI | ||
| debug-mountain | Mountain | Mountain UI | ||
| debug-electron | Electron | Legacy Check | ||
| production | Mountain | Release Path | ||
| release | Mountain | Bundle Path | ||
| web-browser | Browser | Web Path | ||
| bundler-preparation | - | - | ||
| swc-bundle | - | - | ||
| oxc-bundle | - | - |
Deployment Strategies
Four deployment modes from development to production.
Development
Change a file, see it instantly. Hot-reload in Tauri with the Sky dev server. No manual rebuilds needed.
bash Maintain/Dev-Mountain.shDebug Build
Full debug symbols for stepping through code. Three profiles: Browser, Mountain, and Electron.
bash Maintain/Debug/Build.sh --profile debug-mountainRelease Build
Optimized release packaging path. Public signing and verification artifacts are still being prepared.
bash Maintain/Release/Build.sh --profile productionWeb Deployment
Run Land in the browser without installing anything. No native shell needed.
bash Maintain/Release.sh --profile web-browser