0.9.0 (2025-08-15)

Added

• RFC 9110 compliant Retry-After header support with exponential backoff and jitter
• Retry-After header value exposed in error objects for better observability
• FgaError now exposes Retry-After header value via getRetryAfterHeader() method

ChangeD

• Enhanced retry strategy with delay calculation
• BREAKING: Maximum allowable retry count is now enforced at 15 (default remains 3)
• BREAKING: Configuration.minimumRetryDelay() now requires non-null values and validates input, throwing IllegalArgumentException for null or negative values
• Migration Guide:%0A%0A - Update error handling code if using FgaError properties - new getRetryAfterHeader() method available
• Note: Maximum allowable retries is now enforced at 15 (validation added to prevent exceeding this limit)
• IMPORTANT: Configuration.minimumRetryDelay() now requires non-null values and validates input - ensure you're not passing null or negative Duration values, as this will now throw IllegalArgumentException. Previously null values were silently accepted and would fall back to default behavior at runtime

Fixed

• Fixed issue where telemetry metrics are not being exported correctly #590
• Fixed issue with non-transactional write error handling #573

Feature

• Implements feature to improve the retry strategy #155