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

[ucatbas]

Summary by CodeRabbit

• Documentation

  • Updated API documentation and version references to v1.6.3.

• Chores

  • Routine version bump from v1.6.2 to v1.6.3.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates the API version from v1.6.2 to v1.6.3 across documentation, specification files, and the internal version constant. The changes are purely metadata updates with no functional or structural modifications.

Changes

Cohort / File(s)	Summary
API Documentation Files docs/api-reference/apidocs.swagger.json, docs/api-reference/openapi.json, docs/api-reference/openapiv2/apidocs.swagger.json	Updated info.version field from v1.6.2 to v1.6.3 across all API specification documents.
Internal Version Constant internal/info.go	Updated exported Version constant from "v1.6.2" to "v1.6.3".
Proto API Definition proto/base/v1/openapi.proto	Updated OpenAPI swagger info version from v1.6.2 to v1.6.3.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• build: version info update #1737: Performs identical version bump across the same files (docs/api-reference apidocs, openapiv2, internal/info.go, proto/base/v1/openapi.proto)
• chore: update version to v1.6.0 in API docs and internal info file #2716: Executes the same code-level change updating API/version constant and OpenAPI/swagger files
• docs: update API version to v1.3.8 in swagger files #2226: Updates API/version strings in internal/info.go and swagger/openapi specification files

Suggested reviewers

• tolgaozen

Poem

🐰 A version hops from six-point-two to six-point-three,
Through swagger docs and proto files, consistent as can be,
No logic bent, no features new, just metadata so neat,
Another patch release complete—the version's now up to treat!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the version to v1.6.3 across API documentation and internal files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update/api-version-to-v1.6.3

---

No actionable comments were generated in the recent review. 🎉

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.64%. Comparing base (0ea20f5) to head (f4b59d0).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2780      +/-   ##
==========================================
+ Coverage   82.61%   82.64%   +0.03%     
==========================================
  Files          74       74              
  Lines        8125     8125              
==========================================
+ Hits         6712     6714       +2     
+ Misses        894      892       -2     
  Partials      519      519              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.