Skip to content

Latest commit

 

History

History
66 lines (44 loc) · 3.51 KB

File metadata and controls

66 lines (44 loc) · 3.51 KB

Changelog

Unreleased

v0.3.1

Fixed

  • Schema publishing is now a completed part of the shipped release path rather than a post-release manual recovery step.
  • The GitHub Pages schema publication workflow now resolves pinned schema constants and step outputs correctly for both tag-driven and manual runs.
  • README release badges now match the Sheaft header pattern and point at the current Bering release line.
  • Release-facing docs now consistently describe v0.3.1 as the current product line carrying the published 1.1.0 schema contracts.

v0.3.0

Added

  • Versioned public schema contract evolution to io.mb3r.bering.model@1.1.0 and io.mb3r.bering.snapshot@1.1.0 without mutating the preserved 1.0.0 contracts.
  • Typed public topology metadata for stable edge identity, service placements, shared fate-domain references, edge resilience policy, observed latency/error summaries, policy scope, and richer endpoint fidelity.
  • Versioned contracts-pack and release-manifest plumbing aligned with the new schema tree and pinned 1.1.0 digests.
  • Documentation, migration guidance, examples, and schema publishing workflow updates aligned with the 1.1.0 contract line.

v0.2.0

Added

  • Evidence-weighted runtime reconciliation for trace gaps, including conservative guardrail_union publication, raw_window and stable_core views, and machine-readable reconciliation reports.
  • Bounded JSON persistence for runtime reconciliation state so long-running sessions do not retain retired entities indefinitely.
  • Documentation and planning artifacts for the reconciliation minor, including runtime config guidance and an ADR.

v0.1.0

First public product release of Bering.

Highlights

  • Batch discovery from normalized trace input, OTEL trace input, and explicit topology_api inputs.
  • Artifact validation against pinned public JSON schemas.
  • Runtime service with OTLP/HTTP ingest, optional OTLP/gRPC ingest, health endpoints, Prometheus metrics, and rolling snapshot emission.
  • Discovery overlays for additive metadata such as labels, weights, predicate references, and replica overrides.
  • Example artifacts, runtime config, collector wiring, Prometheus scrape config, and Grafana dashboard checked into the repository.

Product vs schema versioning

  • Product release tag: v0.1.0
  • Public schema contracts emitted by this release remain:
    • io.mb3r.bering.model@1.0.0
    • io.mb3r.bering.snapshot@1.0.0
  • Schema publishing to GitHub Pages remains a separate operation under schema-v1.0.0

Packaging and install surface

  • Reproducible release archives via GoReleaser for linux/amd64, linux/arm64, darwin/amd64, darwin/arm64, and windows/amd64.
  • Release payload includes checksums, SBOMs, contracts pack, OCI image metadata, Helm chart metadata, and release-manifest.json.
  • Explicit install path documented for release binaries, source builds, OCI image usage, Helm usage, and offline contracts pack consumption.

Sheaft integration path

  • The primary downstream handoff remains the stable model artifact io.mb3r.bering.model@1.0.0.
  • Checked-in examples and README commands show the expected handoff into Sheaft.

Known limits

  • Bering stops at discovery and publishing; it does not perform simulation, gating, or chaos orchestration.
  • Runtime mode intentionally keeps memory bounded to a single active tumbling window plus the previous emitted snapshot.
  • Late spans and in-memory caps are operational tradeoffs surfaced through metrics and logs, not hidden retries or buffering guarantees.