Bump health, launcher, and logz dependencies from v0.9.0 to v1.0.1 and update go directive from 1.25 to 1.26. API committed as stable; no code changes. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.4 KiB
2.4 KiB
Changelog
All notable changes to this module will be documented in this file.
The format is based on Keep a Changelog, and this module adheres to Semantic Versioning.
1.0.2 - 2026-05-12
Changed
health,launcher, andlogzdependencies bumped from v0.9.0 to v1.0.1.godirective updated from 1.25 to 1.26.
0.9.0 - 2026-03-18
Added
Configstruct — Valkey connection settings loaded from environment variables:VK_ADDRS(required, comma-separated server addresses),VK_PASSWORD(authentication password),VK_DB(database index, default0),VK_CLIENT_CACHE_MB(per-connection client-side cache size in MB, default0disables caching)Providerinterface —Client() valkey.Client; for consumers that only need access to the nativevalkey-goclientComponentinterface — embedslauncher.Component,health.Checkable, andProvider; the full lifecycle-managed surface registered with the launcherNew(logger logz.Logger, cfg Config) Component— constructor; returns aComponentready forlc.AppendOnInit— constructs thevalkey-goclient fromConfig; enables client-side caching whenCacheSizeEachConn > 0OnStart— verifies connectivity by issuing aPINGcommand; returns an error if the ping failsOnStop— callsclient.Close()for graceful shutdownHealthCheck(ctx context.Context) error— issuesPING; returns an error if the client is nil or the command failsName() string— returns"valkey"Priority() health.Level— returnshealth.LevelDegraded; a cache outage degrades service rather than halting it
Design Notes
- The native
valkey-goclient is exposed directly viaClient()with no wrapping or re-exported command subset; callers use the full command-builder API and own all serialisation and key namespacing. Provider/Componentsplit follows the framework pattern: injectProviderinto repositories and services, injectComponentonly at the lifecycle registration site.- Health priority is
LevelDegradedby design — callers must handle cache misses by falling back to the primary datastore rather than treating a Valkey outage as fatal.