OpenFGA
v1.17.1Securityv1.17.1 is a focused patch fixing two correctness bugs: stale cache reads and broken continuation tokens with pipe characters in type names.
breakingAudit type names with '|' if pagination was silently breaking
If your FGA model uses type names containing the pipe character '|', continuation tokens were being deserialized incorrectly. This could cause ListObjects or similar paginated calls to return incomplete or wrong results without throwing obvious errors. Upgrade to v1.17.1 and re-test any pagination flows that touch those type names.
securityStale cache reads could return incorrect authorization decisions — patch now
The iterator cache was using write time rather than query start time as the LastModified anchor, meaning cached entries could persist beyond the intended validity window and serve stale data. In an authorization system, a stale 'allow' decision is a real risk. This is fixed in v1.17.1; upgrade immediately if you run with caching enabled.
enhancementv2Check throttling fallback removed — verify your error handling
Previously, v2Check would fall back to v1 behavior under throttling or validation errors, masking the actual problem. Now it surfaces those errors directly. If your application swallows check errors silently or assumes fallback behavior, you may start seeing errors that were previously hidden. Test under load before rolling out to production.
Key changes (5)
- Fixed stale-read bug in iterator cache: query start time now anchors the LastModified timestamp, preventing cached entries from surviving longer than intended
- Fixed continuation token deserializer failing when type names contain the '|' character, which would silently break pagination
- v2Check no longer falls back to v1 behavior when throttling or validation errors occur, enforcing stricter execution semantics
- Go toolchain bumped to 1.26.4 and grpc-health-probe updated to v0.4.52
- Caching documentation updated to reflect current behavior