Skip to content

Releases: orelvis15/cavs

v1.3.0

Choose a tag to compare

@github-actions github-actions released this 10 Jul 02:51

Full Changelog: v1.2.0...v1.3.0

CAVS Desktop 1.1.0

Choose a tag to compare

@github-actions github-actions released this 10 Jul 02:46

Native installers for Windows, macOS and Linux. See the assets below.

CAVS Godot plugin 0.1.2

Choose a tag to compare

@github-actions github-actions released this 09 Jul 21:10

Full Changelog: v1.2.0...plugins-v0.1.2

CAVS Desktop 1.0.0

Choose a tag to compare

@github-actions github-actions released this 09 Jul 21:18

Native installers for Windows, macOS and Linux. See the assets below.

v1.2.0

Choose a tag to compare

@github-actions github-actions released this 08 Jul 18:40

Full Changelog: v1.1.0...v1.2.0

Full Changelog: v1.1.0...v1.2.0

CAVS v1.1.0 — Practical Patch Policy Benchmark

Choose a tag to compare

@github-actions github-actions released this 08 Jul 14:39

The practical patch policy benchmark release.

CAVS now benchmarks against practical pairwise patch policies — adjacent-only updates, skip-heavy and warm-cache scenarios, base-version hubs and storage-budgeted hot pairs — instead of relying on the theoretical all-pairs O(N²) argument. The all-pairs graph stays only as the labeled theoretical one-hop baseline; every pairwise number is a real diff, applied and byte-verified.

Added

  • cavs bench patch-policy: policy-level comparison with real per-engine measurements (cavsplan built in; bsdiff, xdelta3, butler-offline when installed — missing tools skip with a recorded reason, never fatal).
  • Policies: adjacent, sparse dyadic ladder (--ladder-mode aligned|dense), base hub (--base-policy first|middle|latest-major|fixed:<id>|auto), hot pairs with storage budgets (--hot-pairs latest:K|traffic-top:K, --patch-storage-budget 1GiB|2x-latest-build), all-pairs one-hop baseline, and the CAVS content-addressed route.
  • Traffic models (adjacent-heavy, skip-heavy, live-service-weekly, major-release, random, custom:file.toml) with deterministic weighted expansion; client states cold-cache-with-previous-install and warm-cache.
  • cavs patch-policy graph|simulate|explain (replay another traffic model with no re-diffing) and cavs bench gen-stream.
  • Reports: summary.md/json (avg/P95/P99, steps, coverage), per-edge and per-query CSVs, storage/traffic/apply-chain reports, replayable patch_graph.json, plus a results README.md.
  • Route planner patch-chain risk penalty so multi-step chains are never chosen over a one-step route for a few KiB.
  • New docs: PATCH_POLICY_BENCHMARK, PRACTICAL_PAIRWISE_DIFFS, PATCH_GRAPH_POLICIES, TRAFFIC_MODELS, STORAGE_BUDGET_POLICIES.

Changed

  • README, BENCHMARKS and comparison docs no longer imply that all pairwise diff systems require O(N²) patches: O(N²) now refers specifically to the all-pairs one-hop baseline, and practical pairwise policies are first-class benchmark baselines.

Measured 10-version results (adjacent-heavy, skip-heavy, warm-cache) are in docs/results/v1.1.0/patch-policy/ and docs/BENCHMARKS.md.

CAVS v1.0.0 — Release Certification Suite

Choose a tag to compare

@github-actions github-actions released this 07 Jul 21:06

CAVS v1.0.0 turns CAVS into a stable local build-update engine and certification toolkit. It can compare update routes, verify byte-identical reconstruction, certify Godot PCK workflows, detect regressions, analyze SteamPipe-style update behavior, validate workspace/depot layouts, and export reproducible reports — without requiring a CDN or hosted service.

Highlights

  • New cavs certify release-readiness suite.
  • Certification profiles: quick, standard, release, strict, ci.
  • Deterministic reproducibility bundles.
  • Route certification across cold install, warm cache, previous install, low RAM and slow HDD states.
  • Godot PCK certification using the real plugin API (CavsClient.fetch / fetch_async / ensure_pack).
  • Regression guard with absolute noise floor for timing/RAM metrics.
  • v1.0.0 public trial guide at /try.

Try it

cavs certify --old ./Build_v1 --new ./Build_v2 --profile release --out ./certification

Exit codes are frozen for v1.x: 0 pass · 1 fail · 2 warnings · 3 missing dependency · 4 invalid input · 5 internal error.

Measured (reproducible)

From the deterministic v1.0.0 suite (docs/results/v1.0.0/, regenerable with scripts/run-all.sh): a 125.83 MiB build with ~2% drift certifies end-to-end under the strict profile — 2.26 MiB .cavsplan network (−98.2% vs full download), 214 ms verified byte-identical apply, 0 files rewritten on no-op reapply, every corruption smoke case rejected cleanly, and the Godot PCK reconstructed byte-identically on every route.

Docs

Certification guide · Try CAVS · CI recipes · Compatibility policy (v1.x freeze) · Reproducibility · Godot plugin · CHANGELOG

Notes

CAVS v1.0.0 remains a local build-update engine and analysis toolkit. It is not a CDN, marketplace, DRM system, SteamPipe clone or itch.io replacement; SteamPipe-style figures are estimates from a public model, never Valve's implementation.

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 07 Jul 17:57

Full Changelog: v0.8.0...v0.9.0

Full Changelog: v0.8.0...v0.9.0

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 07 Jul 13:09

Full Changelog: v0.7.0...v0.8.0

Full Changelog: v0.7.0...v0.8.0

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 06 Jul 21:25

Full Changelog: v0.6.0...v0.7.0

Full Changelog: v0.6.0...v0.7.0