Skip to content

v0.25.1

Latest

Choose a tag to compare

@applied-ai-release-bot applied-ai-release-bot released this 07 Aug 15:30

🐛 Bug Fix

📝 Documentation

🔩 Dependency Updates

Notes

Timestamp date filters now return different rows (affected versions 0.5.1–0.25.0). With a bare date or date-only string, != matched the day it was asked to exclude, > behaved like >=, and <= behaved like <. Day boundaries also followed the host timezone rather than UTC, so the same filter resolved differently by machine. All of it failed silently. If you compensated for the old behavior, remove the workaround; if you assert on generated query strings, expect them to change. datetime, full ISO string, and Unix timestamp filters were never affected.

exists() now raises RedisSearchError instead of leaking raw redis-py exceptions. create() already wrapped every other Redis failure this way; the existence check was the one path that escaped. Code catching redis.exceptions.ResponseError around create() — or around a SemanticCache, MessageHistory, SemanticMessageHistory, or SemanticRouter constructor, all of which call create() — should catch RedisSearchError and read __cause__ for the original. This includes NoPermissionError handlers, since that subclasses ResponseError.