This release adds 3 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+2 more
Summary
AI summaryUpdates Experimental within 0.2.0, What changed, and Stable within 0.2.0 across a mixed release.
Full changelog
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
[email protected] - added strict contract support for
[email protected] - kept
1.0.0contract pins, digests, and fail-stop semantics unchanged as the baseline line - added versioned
analysisconfig1.1and a separate Sheaft fault contract1.0 - implemented placement-aware, edge-aware, and fault-profile-aware analysis using typed
1.1.0metadata - extended the existing
analysis.baselinesflow so a primary1.1.0artifact can be compared directly against1.0.0or1.1.0baseline artifacts - added additive reporting for advanced metrics, assertions, blast radius, and non-comparable baseline diffs
Stable within 0.2.0
- strict acceptance of
[email protected] - strict acceptance of
[email protected] - strict acceptance of
[email protected] - strict acceptance of
[email protected] - deterministic analysis and baseline comparison for a fixed artifact, config, and seed
1.0.0baseline semantics and1.1.0additive advanced analysis behavior as documented in the consumer semantics docs
Experimental within 0.2.0
- long-running
serve/watchservice mode - local
discoverhelper - OCI image and Helm chart operational conventions
Compatibility with Bering artifacts
Sheaft v0.2.0 is compatible with these upstream contracts:
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/watchare 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
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Sheaft
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]