0.9.1 (2025-10-07)

Fixed

• Override defaultHeaders in ClientConfiguration to return correct type when using method (#226)
• Correctly handle options with no modelID set in readAuthorizationModel (#226)
• Include headers when converting from ClientListRelationsOptions to ClientBatchCheckOptions (#226)

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

0.8.3 (2025-07-15)

Fixed:

• client: fix connectTimeout config (#182)
• client: fix batchCheck error handling (#183)

0.8.2 (2025-07-02)

Added:

• client: allow accessing the internal api client via getApi (#178)

Fixed:

• client: fix BatchCheck ignoring passed in model ID override (#177)

Maven Central Release

0.8.2-beta.1 (2025-07-01)

• feat(client): allow accessing the internal api client via getApi (#178)
• fix(client): fix passing model ID in BatchCheck (#177)

0.8.1 (2025-02-18)

• fix: use HTTP 1.1 by default (#148)
• fix: ensure default telemetry attributes are sent (#145)
• feat: add batch check telemetry attribute (#143)

0.8.0 (2025-02-07)

• feat!: add support for server-side batchCheck method (#141) - thanks @piotrooo!!
  This is a more efficient way to check on multiple tuples than calling the existing client-side batchCheck. Using this method requires an OpenFGA v1.8.0+ server.
  The existing batchCheck method has been renamed to clientBatchCheck.
  The existing BatchCheckResponse has been renamed to ClientBatchCheckResponse.
• feat: add support for start_time parameter in ReadChanges endpoint (#137)

BREAKING CHANGES:

• Usage of the existing batchCheck method should now use the clientBatchCheck method.

0.7.2 (2024-12-18)

• fix: Ensure executor is shutdown (#133)

0.7.1 (2024-09-23)

• refactor(OpenTelemetry): remove SDK version from meter name
• fix(OpenTelemetry): http.request.method should be enabled by default (#114)
• chore(deps): update dependencies (#110, #111, #112)
• docs(OpenTelemetry): update Metrics and Attributes tables (#115)

0.7.0 (2024-08-28)

• feat: support consistency parameter #107
• Note: To use this feature, you need to be running OpenFGA v1.5.7+ with the experimental flag enable-consistency-params enabled. See the v1.5.7 release notes for details.