# Version 0.1.0a5
Released April 9th, 2026
Added
- Query methods now support
.get()for single-object fetches. Opt-in REST fetching if cache does not contain the object. - New
SQliteBackendin-memory database with file used for persistence. Configurable withbackup_intervalparameter in constructor. - Cache event handler fires listeners as tasks rather than through gathering coroutines.
- Cache
backupandrestoresystem, allowing snapshots of backends to be stored for later use. - Each
~Ruleconstructor now has apredicateparameter to support custom filtering. SQLiteBackendSQL batch size (reads/writes) now configurable in constructor.- New cache events:
BulkChannelEventBulkMemberEventBulkRoleEventChannelInsertEventChannelRemoveEventChannelUpdateEventGuildInsertEventGuildRemoveEventGuildUpdateEventMemberInsertEventMemberRemoveEventMemberUpdateEventPersistEventRoleInsertEventRoleRemoveEventRoleUpdateEvent
- New
bulk_~backend operations:bulk_channelsbulk_membersbulk_roles
- Most backend methods overloaded for type correctness and safety.
- New cache
clearmethod for programmatic clearing of the cache. - Objects in cache automatically deleted if not declared by Discord on startup via
GUILD_AVAILABLE- newprunebackend method.
Breaking Changes
- Removed
startup_~backend operations in favor ofbulk_~operations.
Fixes
- The member query
.where()method parameters were not keyword-only. - Cache event dispatches no longer silently discard exceptions, following
hikari's exception flow cleanly. SQLiteBackenddisconnect logic made more resilient and reconnect-correct.- Cache
subscribe,unsubscribe, andlisteneventparameter acceptsEventTobjects, not instances. - Cache handler method logging used f-strings rather than
%sformatting. RoleQuerydocstring fixed to reflect roles, not messages.SQLiteBackendmember-related methods now made atomic with user storage.SQLiteBackendnow properly drains queue on disconnect and backup.- All
SQLiteBackendwrite errors properly propagated through all pending event listeners.