这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@tolgaozen
Copy link
Member

@tolgaozen tolgaozen commented Jun 5, 2025

Summary by CodeRabbit

  • Documentation

    • Updated API documentation to reflect version v1.4.0.
  • Chores

    • Incremented version number to v1.4.0 across project files.

@coderabbitai
Copy link

coderabbitai bot commented Jun 5, 2025

Walkthrough

This change updates the Permify API version from "v1.3.9" to "v1.4.0" across documentation files, the internal version constant, and the OpenAPI proto file. No modifications were made to API endpoints, schemas, or other logic—only the version string was incremented.

Changes

File(s) Change Summary
docs/api-reference/apidocs.swagger.json,
docs/api-reference/openapiv2/apidocs.swagger.json
API version string updated from "v1.3.9" to "v1.4.0" in Swagger JSON documentation
internal/info.go Internal version constant updated to "v1.4.0"
proto/base/v1/openapi.proto OpenAPI proto version string updated to "v1.4.0"

Possibly related PRs

  • Permify/permify#1530: Updates API version string and internal version constant in the same files.
  • Permify/permify#1910: Also bumps API version and internal constant without other changes.
  • Permify/permify#2226: Updates version strings in Swagger docs, proto, and internal constant, differing only in version number.

Poem

A hop and a skip, the version ascends,
From 1.3.9 to 1.4.0, the journey extends.
No code did we touch, just numbers anew,
The docs and the proto now proudly in view.
🐇✨ Version bumps are quick, but still worth a cheer,
For every new hop brings release day near!


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b521a1c and 3c6073d.

⛔ 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)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Analyze (go)
  • GitHub Check: Test with Coverage
  • GitHub Check: Test with Coverage
🔇 Additional comments (4)
internal/info.go (1)

26-26: Internal version bumped to v1.4.0
Internal version constant has been correctly updated. Ensure that related documentation and Swagger JSON files also reflect this version.

proto/base/v1/openapi.proto (1)

12-12: OpenAPI spec version updated to v1.4.0
The OpenAPI version string now matches the release. Confirm that any generated clients or API docs are regenerated with this new version.

docs/api-reference/openapiv2/apidocs.swagger.json (1)

6-6: API version bump in documentation
Updated the version field from "v1.3.9" to "v1.4.0" to reflect the new release. This aligns with the changes in other docs and the internal version constant.

docs/api-reference/apidocs.swagger.json (1)

6-6: Version bump applied correctly. The API version string has been updated to "v1.4.0" as intended.

✨ Finishing Touches
  • 📝 Generate Docstrings

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants