chore: update version to v1.6.10 in API docs and internal info file

[omer-topal]

Summary by CodeRabbit

• Chores

  • Released version v1.6.10 with updated API documentation and specifications across all formats

• Refactor

  • Modified template rendering to use plain text processing, changing how special characters are handled in template output without HTML-specific escaping

[coderabbitai]

📝 Walkthrough

Walkthrough

Version metadata is bumped from v1.6.9 to v1.6.10 across API documentation and internal version constants. Additionally, the template engine in bundle operations is switched from html/template to text/template to change escaping behavior.

Changes

Version Bump to v1.6.10

Layer / File(s)	Summary
API Documentation Metadata docs/api-reference/apidocs.swagger.json, docs/api-reference/openapi.json, docs/api-reference/openapiv2/apidocs.swagger.json, proto/base/v1/openapi.proto	OpenAPI and Swagger specification version fields updated from v1.6.9 to v1.6.10.
Internal Version Constant internal/info.go	Version constant updated from v1.6.9 to v1.6.10, affecting banner and release metadata output.

Template Engine Change in Bundle Operations

Layer / File(s)	Summary
Template Package Implementation pkg/bundle/bundle.go	Template engine import changed from html/template to text/template, disabling HTML-specific escaping in relationship and attribute template rendering within Operation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Permify/permify#2739: Updates API/OpenAPI metadata version and internal Version constant in the same files.
• Permify/permify#2828: Updates API/OpenAPI version strings and internal/info.go's Version constant across identical documentation and code files.
• Permify/permify#2741: Performs the same version bump pattern across docs, internal/info.go, and proto OpenAPI specs.

Suggested reviewers

• ucatbas

Poem

🐰 A version hops from point-six-nine,
To one-zero, oh how fine!
And templates shed their HTML chains,
Plain text now flows through bundle's veins.
Bump and switch—the release is neat! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the version from v1.6.9 to v1.6.10 across API documentation files and internal configuration.
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update/api-version-to-v1.6.10

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[coderabbitai]

🧹 Nitpick comments (1)

pkg/bundle/bundle.go (1)

20-44: ⚡ Quick win

Extract a shared template-render helper to eliminate 4-way duplication.

All four loops share identical parse → execute → buffer logic; only the downstream converter (tuple.Tuple vs attribute.Attribute) differs. A small helper avoids having to touch four places the next time the template rendering needs to change (e.g., adding a FuncMap, tweaking error messages, or adding options).

♻️ Proposed refactor

+// renderTemplate parses and executes a single template string against the provided arguments,
+// returning the rendered result.
+func renderTemplate(s string, arguments map[string]string) (string, error) {
+	tmpl, err := template.New("template").Parse(s)
+	if err != nil {
+		return "", err
+	}
+	var buf bytes.Buffer
+	if err = tmpl.Execute(&buf, arguments); err != nil {
+		return "", err
+	}
+	return buf.String(), nil
+}

Then each loop body collapses to:

-		tmpl, err := template.New("template").Parse(w)
-		if err != nil {
-			return tb, ab, err
-		}
-		var buf bytes.Buffer
-		err = tmpl.Execute(&buf, arguments)
-		if err != nil {
-			return tb, ab, err
-		}
-		t, err := tuple.Tuple(buf.String())
+		rendered, err := renderTemplate(w, arguments)
+		if err != nil {
+			return tb, ab, err
+		}
+		t, err := tuple.Tuple(rendered)

(and equivalently for the three other loops, substituting attribute.Attribute where appropriate)

Also applies to: 56-80, 92-116, 128-152

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@pkg/bundle/bundle.go` around lines 20 - 44, The four loops in
pkg/bundle/bundle.go duplicate parse → execute → buffer logic; extract a small
helper (e.g., renderTemplate(templateStr string, args interface{}) (string,
error)) and use it from each loop so you only call renderTemplate(w, arguments)
then pass the returned string into the downstream converter (tuple.Tuple or
attribute.Attribute) before calling wtc.Add / atc.Add / etc.; ensure the helper
centralizes template.New(...).Parse and tmpl.Execute error handling (and can
later accept a FuncMap) so the loop bodies become just a call to renderTemplate
plus the existing converter and Add calls.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@pkg/bundle/bundle.go`:
- Around line 20-44: The four loops in pkg/bundle/bundle.go duplicate parse →
execute → buffer logic; extract a small helper (e.g., renderTemplate(templateStr
string, args interface{}) (string, error)) and use it from each loop so you only
call renderTemplate(w, arguments) then pass the returned string into the
downstream converter (tuple.Tuple or attribute.Attribute) before calling wtc.Add
/ atc.Add / etc.; ensure the helper centralizes template.New(...).Parse and
tmpl.Execute error handling (and can later accept a FuncMap) so the loop bodies
become just a call to renderTemplate plus the existing converter and Add calls.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 376f8113-8c73-451a-8345-df865545ba9b

📥 Commits

Reviewing files that changed from the base of the PR and between b6fdfe2 and 256c7a2.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (7)

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