build: version info change

[tolgaOzen]

Summary by CodeRabbit

• New Features
  • Updated API version from v1.2.2 to v1.2.3, indicating minor enhancements or bug fixes.
• Documentation
  • Revised API documentation to reflect the new version number without changes to endpoints or parameters.

[coderabbitai]

Walkthrough

The pull request includes updates to the version number across several files related to the Permify API, changing it from "v1.2.2" to "v1.2.3". This change applies to the API documentation files (apidocs.swagger.json, openapiv2/apidocs.swagger.json), the internal version constant in info.go, and the OpenAPI specification file (openapi.proto). The updates are semantic in nature, with no alterations to the API structure, endpoints, or functionality.

Changes

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

Possibly related PRs

• build: version info update #1762: The changes in this PR involve updating the version number in the same files (apidocs.swagger.json, internal/info.go, and proto/base/v1/openapi.proto) from "v1.2.0" to "v1.2.1", which is directly related to the version update in the main PR from "v1.2.2" to "v1.2.3".
• build: version info update #1790: This PR also updates the version number in the same files from "v1.2.1" to "v1.2.2", showing a continuous progression in versioning that aligns with the changes in the main PR.

🐇 In the meadow, we hop and play,
With version numbers on display.
From "two-two" to "two-three,"
A little change, oh so free!
Documentation shines so bright,
As we bound into the night! 🌙✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f8e919d and b1531fb.

⛔ 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

---

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.