Source, provenance and support

Support and versioning policy

In reviewUpdated 2026-11-15Trust Center

In review. This record, and the tools and files it cites, are on a review branch. They are not in the main source tree yet, so you cannot check them in a copy of the main source today.

How Aster is versioned, how long each release is supported, how security fixes are delivered, and what to expect before 1.0.

The Aster Runtime is provided as is under the Aster Runtime EULA, and the SDK and examples under the MIT licence; both are maintained by Barnyard Greens LLC. This document describes the engineering policy we intend to follow, not a warranty or a service level. Any paid support is a separate offer with its own terms, which are not set here. Status: proposed, takes effect at 1.0.

Pre-1.0 caveats (today)

  • The current version is 0.x (version = "0.1.0" in rust/Cargo.toml). The root README.md states that 1.0 is not released and that prototype signatures are not frozen.
  • Until 1.0, any release can change the public API. We still list breaking changes in the release notes.
  • Pre-1.0 releases are supported by fixing forward: security fixes land in the latest release and the development head only. We do not backport to older 0.x versions unless the maintainers decide otherwise.
  • Crate names are not final and can change before 1.0.

Versioning (from 1.0)

Semantic Versioning 2.0.0: MAJOR.MINOR.PATCH.

ChangeVersion bump
Incompatible public API or documented-behavior changeMAJOR
Backward-compatible featuresMINOR
Backward-compatible fixes, including security fixesPATCH

Rendering output is part of the contract only where the documentation says so (for example documented oracle-exact paths). Changes to output outside those guarantees are listed in the release notes. Optional Cargo features such as net-sync and persist follow the same versioning.

Support window

Release lineReceives
Latest MINOR of the current MAJORall fixes, including security
Previous MINORs of the current MAJORsecurity fixes only, for 12 months after the next MINOR ships
Previous MAJORsecurity fixes only, for 12 months after the new MAJOR's first release, and for longer where the CRA support period requires it

For EU purposes the support period of each major version is at least five years from its first release, and its security updates stay available for 10 years or the remainder of the support period, whichever is longer (EU Cyber Resilience Act readiness). We will state the end-of-support date in the release notes for each major version when it ships. These are proposals for a small team; a longer window would be a separate decision.

Security fixes

  • Handled under Security policy and Vulnerability handling policy: triage within 15 business days, fix targets by severity (30 days critical, 60 days high).
  • A fix ships as a PATCH release of every supported line, signed (Releases: signing, provenance and verification), with an advisory and an updated SBOM and VEX.
  • Security fixes are free during the support window.
  • We do not silently change behavior in a patch release to fix a security flaw without saying so in the release notes.

Toolchain (MSRV) policy

  • Aster builds with the pinned Rust toolchain recorded in the build image (currently 1.98.0) and edition 2024.
  • The minimum supported Rust version equals the pinned toolchain. We raise it in MINOR releases only, never in a PATCH, and list the new minimum in the release notes. We do not test against older compilers.
  • Platform targets: the platforms in the release notes. Windows and Android shell crates are part of the repository; their support level is stated per release.

Dependencies

Deprecation

A deprecated API stays for at least one MINOR release, with a note and a migration path, before removal in the next MAJOR.

What is not decided

ItemNeeds
Whether to offer paid support at all, and its terms (this also affects the CRA role, see EU Cyber Resilience Act readiness)Barnyard Greens and counsel
Whether we offer extended support past the windows aboveBarnyard Greens
Backports to older linesCase by case, maintainers' decision

Source docs/trust/SUPPORT-POLICY.mdlast changed 2026-11-15

More records

Every record in the Trust Center is public.