Skip to content

development.md

Latest commit

 

History

History
50 lines (31 loc) · 2.22 KB

development.md

File metadata and controls

50 lines (31 loc) · 2.22 KB
Raw

Development

Requirements

  • Apple silicon and macOS 26 or later.
  • A Swift 6.2-compatible Xcode toolchain.
  • Git LFS.

Dependency versions are recorded in Package.resolved.

Build the app

git lfs install --local
git lfs pull
./scripts/build-app.sh
open dist/Studio.app

The build script compiles a release executable and assembles a sandboxed, hardened-runtime app. It chooses an available Apple Development or Developer ID certificate; set STUDIO_SIGNING_IDENTITY to select one explicitly.

A real signing team is required to load the updater framework with library validation enabled. With no suitable certificate, packaging can create an ad-hoc inspection artifact, but that artifact cannot launch. The build does not add a library-validation exception.

For compilation without packaging, run:

swift build

Launching the stack requires the packaged, team-signed app and bundled kernel resource.

Tests

swift test -c release

The regression suite covers lifecycle ownership, shutdown and recovery, probes, configuration expansion, OCI validation, storage cleanup, log streaming, native console selection, listener completion, windows and external links, page confirmations, and updater behavior without starting the full stack.

The September stability audit records the original findings and remediation status. A full VM startup remains a separate local smoke test because hosted runners do not guarantee nested virtualization.

Generated and private data

Generated files belong in .build/ and dist/; neither is committed. VM disks, logs, credentials, and app bundles are ignored. Git LFS tracks the bundled kernel. Downloaded images and writable volumes are runtime data and do not belong in the repository.

Continuous integration

Pushes to main and pull requests run tests, assemble the app, verify its signature and security boundary, and retain a packaging-inspection ZIP for seven days. CI uses GitHub's Apple silicon macos-26 runner and logs the selected toolchain.

Unsigned CI artifacts are for inspection only. Public builds follow the tag, Developer ID signing, notarization, stapling, ZIP, checksum, and signed appcast workflow described in Release setup.