Skip to content

HydraCache 0.65.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 17 Jul 11:38
· 779 commits to main since this release
v0.65.0
edf0fd1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

HydraCache 0.65.0

0.65.0 builds a Redis debt safety net around the standalone RESP facade. It
adds reusable contracts, exhaustive characterization, protocol compatibility
fixtures, and real-process deployment sentinels without adding a Redis command
or claiming a distributed RESP backend.

Highlights

  • Added a backend-agnostic ClientSurface conformance suite so a future RESP
    backend can be evaluated against the same cache semantics.
  • Closed test-exposed isolation defects: tenant-scoped store/native CAS/retry
    keys and atomic quota/store transitions for writes, mismatch, delete, expiry,
    and concurrent updates.
  • Made every Redis conformance row declare an execution route and stable case
    ids, with translator/reducer and RESP2/RESP3 characterization tied to real
    Rust tests.
  • Added a dedicated real-process multi-node gate for cross-endpoint key
    visibility, batch operations, lock acquisition, token-safe release, and TTL
    extension.
  • Added AST-backed documentation checks that reject dangling test references,
    comment-only sentinels, duplicate case ids, missing debt metadata, and
    deployment tests that do not call the dedicated gate helper.
  • Added a frozen v1 minimum-surface catalog plus v2/v3 client-protocol fixtures
    with independent provenance and digest checks, version-envelope validation,
    and proof that older clients never receive v4 conditional result shapes.
  • Added release-evidence and CI governance for all seven work items, including
    the exact dedicated multi-node command and receipt-bound execution.

Compatibility And Scope

  • The supported Redis command set is unchanged.
  • RESP data remains node-local; cross-endpoint key visibility is tracked as
    resp-cross-endpoint-key-visibility.
  • Redis lock safety remains single-endpoint; cross-endpoint acquire,
    release, and extend are tracked as resp-cross-endpoint-lock-safety.
  • The characterized DEL path does not claim atomic ordering against a
    concurrent write; that narrower limitation is tracked as
    resp-del-concurrent-write-atomicity.
  • Redis Cluster, general Lua, ownership routing, and a distributed RESP backend
    remain outside this release.

Verification

Run the ordinary workspace gates plus:

cargo xtask doc-check
cargo test -p xtask --test doc_check redis_compat --locked
$env:HYDRACACHE_RUN_REDIS_RESP_MULTINODE_E2E = '1'
cargo test -p hydracache-server --test redis_resp_multinode --locked -- --nocapture
Remove-Item Env:\HYDRACACHE_RUN_REDIS_RESP_MULTINODE_E2E -ErrorAction SilentlyContinue

CI executes the multi-node target through the registered exact-command receipt:

cargo run -p xtask --locked -- evidence-run --release 0.65 --gate env.hydracache-run-redis-resp-multinode-e2e

The authoritative scope and debt-payment rules are recorded in
V0_65_REDIS_DEBT_SAFETY_NET_PLAN.md,
redis_compat_conformance.json,
GATES.md, and TESTING.md.

Assets 2
Loading