Regenerated OpenAPI doc

[tisnik]

Description

Regenerated OpenAPI doc

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Summary by CodeRabbit

• Documentation
  • Updated API specification examples to reflect llama stack version “0.2.21” for the version field in the info response.
  • This is a documentation-only adjustment to keep example values current for consumers referencing the OpenAPI schema.
  • No functional or behavioral changes to the API; existing integrations are unaffected.

[coderabbitai]

Walkthrough

Updated docs/openapi.json to add a new example value "0.2.21" for InfoResponse.llama_stack_version. No other changes to the OpenAPI spec or exported entities.

Changes

Cohort / File(s)	Summary of Changes
OpenAPI spec updates docs/openapi.json	Added example value "0.2.21" to InfoResponse.llama_stack_version examples; no structural or functional spec changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• LCORE-304: OpenAPI documentation in Markdown #259 — Also touches OpenAPI documentation around InfoResponse; likely related to versioning/spec alignment.

Poem

A nibble of docs, a version to sing,
"0.2.21"—a bright, tidy thing.
I thump in approval, specs neat and clean,
Carrots and schemas: a well-groomed scene.
Hop, hop—release notes gleam! 🥕✨

Pre-merge checks and finishing touches

✅ 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 succinctly conveys that the OpenAPI documentation was regenerated to include the updated example value in docs/openapi.json. It directly matches the primary change in the pull request and avoids unnecessary detail or noise. It is concise, clear, and sufficient for a quick scan of the commit history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 43dd8d6 and dc38b15.

📒 Files selected for processing (1)

• docs/openapi.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: build-pr
• GitHub Check: e2e_tests

---

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