build: version info update

[tolgaOzen]

Summary by CodeRabbit

• New Features
  • Updated API documentation to version 1.0.6, indicating potential new features, improvements, or bug fixes.
• Bug Fixes
  • Minor enhancements reflected in the version update across various documentation files.
• Chores
  • Incremented version numbers in multiple documentation files to maintain consistency in the API's versioning.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
permify	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 9, 2024 8:16am

[coderabbitai]

Walkthrough

The pull request introduces a minor version update for the Permify service, changing the version number from "v1.0.5" to "v1.0.6" across multiple documentation and internal files. This update reflects an incremental progression in the API's versioning, indicating potential new features, improvements, or bug fixes. The overall structure and content of the affected files remain unchanged aside from the version increment.

Changes

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

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant API
    participant Documentation

    User->>API: Request API version
    API->>Documentation: Check current version
    Documentation-->>API: Return version "v1.0.6"
    API-->>User: Respond with version "v1.0.6"

Loading

Poem

🐰 In the meadow, changes bloom,
A version rise, dispelling gloom.
From five to six, we hop along,
With every leap, we sing a song.
New features sprout, like flowers bright,
In the Permify world, all feels right! 🌼

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 84d71ed and 5f30c64.

Files ignored due to path filters (1)

• pkg/pb/base/v1/openapi.pb.go is excluded by !**/*.pb.go

Files selected for processing (4)

• docs/api-reference/apidocs.swagger.json (1 hunks)
• docs/api-reference/openapiv2/apidocs.swagger.json (1 hunks)
• internal/info.go (1 hunks)
• proto/base/v1/openapi.proto (1 hunks)

Files skipped from review due to trivial changes (4)

• docs/api-reference/apidocs.swagger.json
• docs/api-reference/openapiv2/apidocs.swagger.json
• internal/info.go
• proto/base/v1/openapi.proto