Skip to content

Orbit v0.9.0

Choose a tag to compare

@github-actions github-actions released this 13 Oct 18:05
· 40 commits to main since this release

npm publication: @cybergarage/orbit@0.9.0 is published. The npm latest tag is 0.9.0, and the registry tarball matches the independently validated artifact.

Source release for the current application-development runtime. GitHub
release creation and npm publication are separate steps.

Added

  • Add public DurableWorkStore and scheduling types for single-owner local
    hosts. Persist schedules, occurrences, stable request IDs, attempts, approvals,
    cancellation and results. Interrupted read work can return to the queue;
    uncertain opaque effects require explicit reconciliation. See
    Durable scheduled work.
  • Add the optional apple provider, AppleFoundationModelsAgent and
    AppleHelperClient, with a separately compiled Swift helper included in the
    package. Support local text generation and alternating text turns on eligible
    Macs; tools, streaming and structured generation remain unsupported. See
    Apple Foundation Models.
  • Add Orbit branding and links to the Orbit App and Orbit Nest projects.

Fixed

  • Support Windows storage registration, writer coordination, migration and
    managed execution with explicit file-flush acknowledgements. Use writable
    file handles for synchronization and preserve native realpath identity,
    including expanded Windows short paths. Explicit unsupported directory-sync
    guarantees still fail; errors are not silently ignored. See
    Platform acknowledgement.

Upgrade notes

  • Pin application dependencies to @cybergarage/orbit@0.9.0 and retain the
    application lockfile. The consumer example now targets this version.
  • Existing v0.8.1 execution APIs remain available. This release does not add a
    Session or execution-journal format migration. Existing or interrupted data
    still requires the applicable storage maintenance
    procedure before changing writers.
  • Windows defaults to file-sync; Linux and macOS retain
    file-and-directory-sync. Hosts requiring the stronger level must request it
    explicitly and handle rejection on unsupported platforms. File-only
    acknowledgement does not establish namespace durability across power loss.
  • Scheduling supplies host storage primitives, not a background daemon or
    calendar/timezone recurrence. Apple model use requires explicit native setup
    and a text-only configuration; other provider installations remain portable.

Validation scope

Deterministic tests and an independently installed package consumer validate the
runtime and distribution surface. Live-provider quality, deployment recovery
and physical power-loss behavior require separate qualification. The existing
stale-lock reclamation race remains documented in
Development.

Full changelog: v0.8.1...v0.9.0