qbit-session-store/CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased] - 0.1.0

First published release. Version numbers are assigned by the shared Gitea Maven workflow from the branch or tag that publishes (see README "Releasing"); the revision property on develop stays 0.1.0-SNAPSHOT until the release merges back.

Added

• In-memory session store provider with LRU eviction
• Table-based session store provider using QQQ tables
• Redis session store provider with native TTL via Jedis
• Custom provider support via QCodeReference
• Sliding expiration (configurable per-provider)
• Scheduled cleanup process for expired sessions
• QBit producer for declarative configuration
• SHARED_REDIS provider: application-scoped shared sessions on the pool owned by the optional qbit-redis QBit, with explicit deployment/application/ authentication-domain namespacing, bounded payloads, atomic GETEX touch, and a runtime service that releases registrations on stop and rebuilds them on restart (docs/SESSION-REGISTRATION.md)
• Explicit QInstance overloads on QSessionStoreQBitContext and application-scoped registration through QSessionStoreRegistry.getInstance(qInstance); two applications in one JVM no longer see each other's sessions
• Health check reports the target application selected by HealthCheckInput

Changed

• Depends on published QQQ core 4.1.0-RC.22 (the first release-line core with QSessionStoreRegistry.getInstance(QInstance)) and qbit-redis 0.1.0-RC.1; the snapshot coordinates used while the shared-session work was in flight (4.1.0-collab-33464d37e-SNAPSHOT, 0.1.0-redis-7fe5492-SNAPSHOT) are gone
• Jedis 7.2.0, Testcontainers 2.0.3, AssertJ 3.27.7 (GHSA-rqfh-9r24-8c9r)
• Hosts that register a provider with core outside a request context must use the explicit QSessionStoreRegistry.getInstance(qInstance) overload