Skip to content

BetterDB-inc/monitor

vsemantic-cache-v0.5.1 scope: semantic-cache Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 3d Monitoring & Metrics
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

prometheus monitoring obsevability redis valkey

ReleasePort's take

Light signal
editorial:auto 3d

The telemetry dependency is now required in semantic-cache-v0.5.1; opting out remains supported.

Why it matters: All deployments must include the telemetry module to remain functional, though opt‑out configuration is still allowed.

Summary

AI summary

Telemetry handling is now required; opting out remains supported.

Changes in this release

Feature Low

Opting out of telemetry remains supported with the existing mechanism.

Opting out of telemetry remains supported with the existing mechanism.

Source: granite4.1:30b@2026-05-31-audit

Confidence: low

Dependency Medium

Telemetry dependency is no longer optional.

Telemetry dependency is no longer optional.

Source: llm_adapter@2026-05-31

Confidence: high

Full changelog

Updated telemetry handled. No longer optional dependency.

Opting out still supported with the same mechanism

Full Changelog: https://github.com/BetterDB-inc/monitor/compare/agent-cache-py-v0.6.1...semantic-cache-v0.5.1

Breaking Changes

  • Telemetry handling changed from optional to required dependency

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track BetterDB-inc/monitor

Get notified when new releases ship.

Sign up free

About BetterDB-inc/monitor

Valkey-first observability with Redis compatibility. Query real-time metrics, analyze slow commands, detect hot keys, and investigate performance issues directly from AI coding assistants.

All releases →

Related context

Earlier breaking changes

  • vagent-v1.5.0 TLS is now mandatory; agent exits with error if `--valkey-tls true` is not set for IAM auth mode.

Beta — feedback welcome: [email protected]