Skip to content

v0.8.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 31 Aug 16:19
· 2 commits to main since this release
v0.8.0
12aa27b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Graviton v0.8.0

Graviton v0.8.0 turns the current pre-1.0 line into a clean, qualified byte-substrate release. It keeps document models, transforms, extraction, search, and workflow state outside the project.

Operational additions

  • authenticated tenant routing, retained-byte quotas, private and explicitly shared deduplication domains, and PostgreSQL row-level security;
  • process, tenant, backend, and optional Redis or Valkey distributed transfer admission;
  • cluster-atomic request and delivered-egress quotas for authenticated HTTP and gRPC;
  • ZIO-native gRPC quota effects with backpressured per-frame egress charging;
  • GVM4 metadata, optional manifest authentication, tenant-domain snapshots, cold-block repair, quarantine inventory, and restore;
  • operator health and telemetry APIs, the loopback Datastar console, Prometheus rules, Grafana dashboard, and qualification matrix;
  • backend fault and law kits, bounded manifest inspection, and backend-native streaming inventory.

Library boundary fixes

  • New IngestPipeline.countHashRechunkSummary and CasIngest.pipelineSummary entry points return explicit ZIO Blocks schema-backed summaries. Their Scala 3.8 suites are enabled and no longer depend on mixed-field dynamic Kyo Record access. The v0.7 method names remain as deprecated binary-compatible shims.
  • The optional graviton-admission-redis_3 module joins the published Maven Central module set.
  • Existing GravitonGrpcServer.scoped overloads remain available; distributed traffic quota wiring is an additive overload.

Clean-store boundary

This is a pre-1.0 clean-store release. Filesystem manifests use GVM4 and reject older envelopes. PostgreSQL starts at immutable V001__graviton.sql, which owns only the Graviton byte, identity, integrity, security, upload, and maintenance substrate. There is no legacy manifest reader, combined-schema migration, or backfill path. Do not point v0.8.0 at a store created by an older development build.

Apply PostgreSQL migrations with ./scripts/migrate-postgres.sh. The runner serializes migrators, records SHA-256 checksums, skips matching applied versions, and fails on drift.

Qualification boundary

Repository CI proves the published tests, packaged server smoke, clean external consumer, migration idempotency, local failure drills, backup and restore, and machine-readable telemetry contracts. It does not establish a universal capacity, latency, recovery, cloud-provider, IdP, ingress, Ceph, RDS, Redis or Valkey failover, or zone-failure claim. Run every target-required gate in deploy/qualification-v1/matrix.json against the exact production image and infrastructure before customer traffic.

Assets 8
Loading