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

[lyleschemmerling]

Summary by CodeRabbit

• Documentation
  • Updated API documentation to version v1.6.1.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

A straightforward version bump from v1.6.0 to v1.6.1 across API documentation files (Swagger/OpenAPI JSON), the internal version constant, and proto OpenAPI configuration. No functional or structural changes.

Changes

Cohort / File(s)	Summary
API Documentation Version Updates docs/api-reference/apidocs.swagger.json, docs/api-reference/openapi.json, docs/api-reference/openapiv2/apidocs.swagger.json	Version string bumped from v1.6.0 to v1.6.1 in the info.version field across all three OpenAPI/Swagger documentation files.
Internal Version Constant internal/info.go	Exported constant Version updated from "v1.6.0" to "v1.6.1".
Proto OpenAPI Configuration proto/base/v1/openapi.proto	Version field in the grpc.gateway.protoc_gen_openapiv2.options.openapiv2_swagger OpenAPI info option updated from v1.6.0 to v1.6.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: update version to v1.6.0 in API docs and internal info file #2716: Performs the same version-bump changes across API documentation, proto OpenAPI, and internal version constant.
• chore: update version to v1.5.1 in API docs and internal info file #2602: Updates API/version strings in the same files (docs, proto, and internal/info.go) following an identical pattern.
• docs: update API version to v1.4.6 across documentation and code files #2560: Bumps API/version strings across Swagger/OpenAPI JSON files, proto OpenAPI, and internal version constant.

Suggested reviewers

• tolgaozen

Poem

🐰 A minor hop from six to six-point-one,
Version strings now match, the bump is done!
Docs, proto, code—all in perfect line,
Consistency achieved, how divine! ✨

🚥 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 accurately describes the main change: updating the API version from v1.6.0 to v1.6.1 across multiple documentation and code 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

---

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.61%. Comparing base (af5ccc9) to head (b07d382).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2739      +/-   ##
==========================================
- Coverage   82.63%   82.61%   -0.01%     
==========================================
  Files          74       74              
  Lines        8125     8125              
==========================================
- Hits         6713     6712       -1     
  Misses        893      893              
- Partials      519      520       +1     

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