Skip to content

Sheaft v0.2.0 technical preview

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Mar 13:42
v0.2.0
f57af5f

Sheaft v0.2.0

v0.2.0 is a technical-preview feature release that adds real dual-line downstream compatibility for Bering 1.0.0 and 1.1.0, while preserving 1.0.0 as the baseline semantics line.

What changed

  • added strict contract support for io.mb3r.bering.model@1.1.0
  • added strict contract support for io.mb3r.bering.snapshot@1.1.0
  • kept 1.0.0 contract pins, digests, and fail-stop semantics unchanged as the baseline line
  • added versioned analysis config 1.1 and a separate Sheaft fault contract 1.0
  • implemented placement-aware, edge-aware, and fault-profile-aware analysis using typed 1.1.0 metadata
  • extended the existing analysis.baselines flow so a primary 1.1.0 artifact can be compared directly against 1.0.0 or 1.1.0 baseline artifacts
  • added additive reporting for advanced metrics, assertions, blast radius, and non-comparable baseline diffs

Stable within 0.2.0

  • strict acceptance of io.mb3r.bering.model@1.0.0
  • strict acceptance of io.mb3r.bering.snapshot@1.0.0
  • strict acceptance of io.mb3r.bering.model@1.1.0
  • strict acceptance of io.mb3r.bering.snapshot@1.1.0
  • deterministic analysis and baseline comparison for a fixed artifact, config, and seed
  • 1.0.0 baseline semantics and 1.1.0 additive advanced analysis behavior as documented in the consumer semantics docs

Experimental within 0.2.0

  • long-running serve / watch service mode
  • local discover helper
  • OCI image and Helm chart operational conventions

Compatibility with Bering artifacts

Sheaft v0.2.0 is compatible with these upstream contracts:

  • io.mb3r.bering.model@1.0.0
  • io.mb3r.bering.snapshot@1.0.0
  • io.mb3r.bering.model@1.1.0
  • io.mb3r.bering.snapshot@1.1.0

Compatibility remains strict. Unsupported schemas, URI mismatches, or digest mismatches are rejected instead of being auto-coerced.

Known limitations

  • no live chaos execution, traffic generation, or new discovery pipeline is introduced in this release
  • explicit legacy predicates remain service-based unless explicit path/journey information exists
  • advanced metrics remain unavailable instead of guessed when the artifact or external contract does not provide the required metadata
  • serve / watch are included for evaluation, not yet as a stable long-term operational contract

First run

./sheaft run \
  --model examples/outputs/snapshot-v1.1.0.sample.json \
  --analysis configs/analysis.v1.1.example.yaml \
  --out-dir out/quickstart-analysis
Assets 18
Loading