Merged
Conversation
Contributor
WalkthroughUpdates the CHANGELOG.md with version 0.7.11 release notes, documenting two bug fixes (empty slice ListObjects test and WriteAssertions limit) and one new feature (--max-types-per-authorization-model flag). Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
rhamzeh
requested changes
Mar 17, 2026
Co-authored-by: Raghd Hamzeh <raghd@rhamzeh.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
CHANGELOG.md (1)
384-385: 🛠️ Refactor suggestion | 🟠 MajorUpdate version comparison links for v0.7.10 and v0.7.11.
The version comparison links at the bottom of the changelog are missing entries for v0.7.10 and v0.7.11. Additionally, the
[Unreleased]link should now point tov0.7.11...HEADinstead ofv0.7.9...HEAD.📝 Proposed fix to update version links
-[Unreleased]: https://github.com/openfga/cli/compare/v0.7.9...HEAD +[Unreleased]: https://github.com/openfga/cli/compare/v0.7.11...HEAD +[0.7.11]: https://github.com/openfga/cli/compare/v0.7.10...v0.7.11 +[0.7.10]: https://github.com/openfga/cli/compare/v0.7.9...v0.7.10 [0.7.9]: https://github.com/openfga/cli/compare/v0.7.8...v0.7.9🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 384 - 385, Update the version comparison links at the bottom of CHANGELOG.md: change the [Unreleased] range from v0.7.9...HEAD to v0.7.11...HEAD, add new comparison links for [0.7.10] and [0.7.11] (pointing to their respective GitHub compare ranges), and update the existing [0.7.9] link if needed to reference v0.7.8...v0.7.9 so the sequence is consistent; locate the lines containing the link labels "[Unreleased]" and "[0.7.9]" and append the new link definitions for "[0.7.10]" and "[0.7.11]".
🧹 Nitpick comments (2)
CHANGELOG.md (2)
18-19: Remove extra blank line for consistent spacing.There are two consecutive blank lines after the v0.7.11 entry, while other version entries use a single blank line separator.
♻️ Proposed fix
- Add --max-types-per-authorization-model flag (`#641`) - Thanks `@nverbos-godaddy` -🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 18 - 19, The changelog has two consecutive blank lines after the "v0.7.11" entry; edit CHANGELOG.md and remove the extra blank line so there is only a single blank line separating the v0.7.11 entry from the next entry (ensure the spacing matches other version entries).
12-17: Consider reordering sections to match the established pattern.The changelog entry has "Fixed" before "Added", while other version entries (e.g., v0.7.7, v0.7.5) consistently use the order: Added, Changed, Fixed. This aligns with Keep a Changelog conventions.
♻️ Proposed reordering
-Fixed: -- Fix local ListObjects tests when expected response is an empty slice (`#645`) -- Limit WriteAssertions to 100 assertions (`#619`) - Added: - Add --max-types-per-authorization-model flag (`#641`) - Thanks `@nverbos-godaddy` +Fixed: +- Fix local ListObjects tests when expected response is an empty slice (`#645`) +- Limit WriteAssertions to 100 assertions (`#619`) +🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` around lines 12 - 17, Reorder the changelog entry so the section headings follow the project's standard sequence: move the "Added:" block above "Fixed:" to produce "Added", then "Changed" (if present), then "Fixed"; specifically swap the current "Fixed:" and "Added:" blocks in the shown diff so the three bullets appear under "Added:" first and "Fixed:" last to match other entries like v0.7.7/v0.7.5.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@CHANGELOG.md`:
- Around line 384-385: Update the version comparison links at the bottom of
CHANGELOG.md: change the [Unreleased] range from v0.7.9...HEAD to
v0.7.11...HEAD, add new comparison links for [0.7.10] and [0.7.11] (pointing to
their respective GitHub compare ranges), and update the existing [0.7.9] link if
needed to reference v0.7.8...v0.7.9 so the sequence is consistent; locate the
lines containing the link labels "[Unreleased]" and "[0.7.9]" and append the new
link definitions for "[0.7.10]" and "[0.7.11]".
---
Nitpick comments:
In `@CHANGELOG.md`:
- Around line 18-19: The changelog has two consecutive blank lines after the
"v0.7.11" entry; edit CHANGELOG.md and remove the extra blank line so there is
only a single blank line separating the v0.7.11 entry from the next entry
(ensure the spacing matches other version entries).
- Around line 12-17: Reorder the changelog entry so the section headings follow
the project's standard sequence: move the "Added:" block above "Fixed:" to
produce "Added", then "Changed" (if present), then "Fixed"; specifically swap
the current "Fixed:" and "Added:" blocks in the shown diff so the three bullets
appear under "Added:" first and "Fixed:" last to match other entries like
v0.7.7/v0.7.5.
|
Documentation Updates 1 document(s) were updated by changes in this PR: Contextual Tuples SupportView Changes@@ -37,13 +37,15 @@
There are limits on the number of contextual tuples: up to 100 per request (as of OpenFGA v1.7.0), and up to 20 per assertion in Write Assertions. Exceeding these limits will result in a request error. [Reference](https://github.com/openfga/openfga/blob/28ed51fb5f6c9e3eb113e15b8b98fb7eb1aa56aa/CHANGELOG.md#L287-L764)
+Additionally, WriteAssertions is limited to a maximum of 100 assertions per request (as of CLI version 0.7.11, released March 17, 2026).
+
### CLI Import Behavior for Write Assertions
-When using the `fga store import` command, there is a limit of 100 assertions per write operation. If you attempt to import a store with more than 100 assertions, the CLI will:
+The CLI enforces a limit of 100 assertions per WriteAssertions request (as of CLI version 0.7.11). When using the `fga store import` command, if you attempt to import a store with more than 100 assertions, the CLI will:
- Write only the first 100 assertions
- Display a warning message: `Warning: N test assertions found, but only the first 100 will be written`
-This limit is enforced by the CLI tool's import functionality, not by the OpenFGA server API itself. If you need to import more than 100 assertions, you will need to make multiple separate write operations.
+This limit is enforced by the CLI tool's WriteAssertions functionality. If you need to import more than 100 assertions, you will need to make multiple separate write operations.
## Specifying Contextual Tuples in Requests
How did I do? Any feedback? |
rhamzeh
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
What problem is being solved?
How is it being solved?
What changes are made to solve it?
References
Review Checklist
mainSummary by CodeRabbit
Bug Fixes
New Features