build: version info update

[tolgaOzen]

Summary by CodeRabbit

• New Features

  • Updated API documentation to version 1.1.9, ensuring users have access to the latest specifications.

• Bug Fixes

  • No functional changes; the API behavior and documentation structure remain consistent with the previous version.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve updating the version number of the Permify API documentation and related files from "v1.1.8" to "v1.1.9". This update is reflected in multiple files, including the API documentation in JSON and OpenAPI formats, as well as a constant in the internal Go file. The structure and content of the API documentation remain unchanged, with no alterations to endpoints, parameters, or response schemas.

Changes

File Path	Change Summary
docs/api-reference/apidocs.swagger.json	Version updated from "v1.1.8" to "v1.1.9"
docs/api-reference/openapiv2/apidocs.swagger.json	Version updated from "v1.1.8" to "v1.1.9"
internal/info.go	Version constant updated from "v1.1.8" to "v1.1.9"
proto/base/v1/openapi.proto	Version updated from "v1.1.8" to "v1.1.9"

Possibly related PRs

• build: version info update #1521: The version number in internal/info.go was updated from "v1.0.3" to "v1.0.4", which is a similar version increment as in the main PR.
• build: version info update #1530: The version number in internal/info.go was updated from "v1.0.4" to "v1.0.5", reflecting a consistent pattern of version updates.
• build: version info update #1554: The version number in internal/info.go was updated from "v1.0.5" to "v1.0.6", continuing the trend of version increments.
• build: version info update #1597: The version number in internal/info.go was updated from "v1.0.6" to "v1.0.7", aligning with the versioning changes in the main PR.
• build: version info update #1626: The version number in internal/info.go was updated from "v1.1.0" to "v1.1.1", which is directly related to the versioning changes in the main PR.
• build: version info change #1643: The version number in internal/info.go was updated from "v1.1.1" to "v1.1.2", indicating a similar version update as in the main PR.
• build: version info update #1667: The version number in internal/info.go was updated from "v1.1.2" to "v1.1.3", reflecting the same versioning pattern.
• fix: subject filtering pagination #1710: The version number in internal/info.go was updated from "v1.1.5" to "v1.1.6", which is consistent with the version updates in the main PR.
• build: version info update #1737: The version number in internal/info.go was updated from "v1.1.7" to "v1.1.8", maintaining the versioning consistency observed in the main PR.

🐰 "Hoppity hop, a version anew,
From eight to nine, we bid adieu!
Documentation shines, all clear and bright,
With every update, we take flight!
So let’s celebrate, with a joyful cheer,
For the Permify API, we hold so dear!" 🐇

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.