chore(proto): update generated SDK with latest Permify definitions

[omer-topal]

Automatically created PR with the latest generated SDK from Permify proto definitions.

Summary by CodeRabbit

• Chores
  • Version bumped to 1.7.0

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9e2eadb2-e1ef-4bae-9037-d308d998f026

📥 Commits

Reviewing files that changed from the base of the PR and between 8ab0291 and 69057c5.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json
• proto/base/v1/openapi.proto

---

📝 Walkthrough

Walkthrough

Package and API version numbers are synchronized and bumped from 1.6.10 to 1.7.0 across package.json and the OpenAPI proto metadata definition.

Changes

Version bump to 1.7.0

Layer / File(s)	Summary
Version metadata update package.json, proto/base/v1/openapi.proto	Version number is incremented from 1.6.10 to 1.7.0 in both package metadata and the OpenAPI proto definition.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Permify/permify-node#425: Both PRs make the same kind of version-bump change in package.json and proto/base/v1/openapi.proto (updating the documented info.version), but main PR advances to v1.7.0 while the retrieved PR updated from v1.6.9 to v1.6.10.
• Permify/permify-node#404: Both PRs update the same proto/base/v1/openapi.proto OpenAPI openapiv2_swagger metadata info.version string (main bumps to v1.7.0; retrieved bumps to v1.6.7).
• Permify/permify-node#408: Both PRs update the proto/base/v1/openapi.proto OpenAPI info.version field (main: v1.6.10→v1.7.0, retrieved: v1.6.7→v1.6.9) with no other functional option changes.

Poem

🐰 A version hop, from ten-point-six,
To seven-point-oh—a perfect mix!
Two files dance in sync with glee,
Release day blooms for all to see! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions updating generated SDK with Permify definitions, but the actual changes only bump package and API versions with no SDK generation or definition updates evident.	Revise the title to accurately reflect the actual changes, such as 'chore: bump version to 1.7.0' or 'chore(release): prepare v1.7.0 release'.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch proto-update/permify-latest

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}