Skip to content

release: v0.7.2 #542

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 11, 2025
Merged

release: v0.7.2 #542

merged 1 commit into from
Jul 11, 2025

Conversation

rhamzeh
Copy link
Member

@rhamzeh rhamzeh commented Jul 11, 2025 •
edited by coderabbitai bot
Loading

Description

Changelog

Fixed:

  • Store tuple files being required (#539)

Includes

What problem is being solved?

How is it being solved?

What changes are made to solve it?

References

Review Checklist

  • I have clicked on "allow edits by maintainers".
  • I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
  • The correct base branch is being used, if not main
  • I have added tests to validate that the change in functionality is working as expected

Summary by CodeRabbit

  • Documentation
    • Updated the changelog to include details for release version 0.7.2, highlighting a fix related to store tuple files.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 11, 2025 •
edited
Loading

Walkthrough

The changelog was updated to document the release of version 0.7.2 on 2025-07-11, including a note about a specific bug fix related to store tuple files. The comparison range for the "Unreleased" section was also updated to reflect the new version.

Changes

File Change Summary
CHANGELOG.md Updated for version 0.7.2 release, added fix for store tuple file requirement (issue #539), and adjusted comparison range for "Unreleased" section.

Sequence Diagram(s)

No sequence diagram is generated since the change is limited to documentation updates.

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@rhamzeh rhamzeh marked this pull request as ready for review July 11, 2025 14:31
@rhamzeh rhamzeh requested a review from a team as a code owner July 11, 2025 14:31
coderabbitai[bot]
coderabbitai bot reviewed Jul 11, 2025
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
CHANGELOG.md (2)

3-3: Consider normalizing heading levels (MD001).

# ➜ #### is a three-level jump that keeps triggering markdownlint (heading-increment).
Switching release headings to ## (or disabling the rule) will silence the linter and improve structural consistency.

-#### [Unreleased](https://github.com/openfga/cli/compare/v0.7.2...HEAD)
+## [Unreleased](https://github.com/openfga/cli/compare/v0.7.2...HEAD)

5-8: Apply the same heading-level fix to the new 0.7.2 section.

Consistent levels avoid future linter noise and make TOC generators happier.

-#### [0.7.2](https://github.com/openfga/cli/compare/v0.7.1...v0.7.2) (2025-07-11)
+## [0.7.2](https://github.com/openfga/cli/compare/v0.7.1...v0.7.2) (2025-07-11)

No content issues detected in the bullet itself. 👍

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c2ce0c4 and d1caba9.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

3-3: Heading levels should only increment by one level at a time
Expected: h2; Actual: h4

(MD001, heading-increment)

@rhamzeh rhamzeh added this pull request to the merge queue Jul 11, 2025
Merged via the queue into main with commit e1b9c49 Jul 11, 2025
22 checks passed
@rhamzeh rhamzeh deleted the release/v0.7.2 branch July 11, 2025 14:37
@coderabbitai coderabbitai bot mentioned this pull request Aug 12, 2025
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@jimmyjames jimmyjames jimmyjames approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@rhamzeh @jimmyjames