Skip to content

Add 'About this Release' section to AI Workspace documentation - #408

Merged
Thushani-Jayasekera merged 6 commits into
wso2:mainfrom
Thushani-Jayasekera:aiws-docs
Aug 6, 2026
Merged

Add 'About this Release' section to AI Workspace documentation#408
Thushani-Jayasekera merged 6 commits into
wso2:mainfrom
Thushani-Jayasekera:aiws-docs

Conversation

@Thushani-Jayasekera

@Thushani-Jayasekera Thushani-Jayasekera commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@Thushani-Jayasekera, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 31c06705-34ad-4d48-9b06-94536d550dd8

📥 Commits

Reviewing files that changed from the base of the PR and between c25df54 and c2a94f5.

📒 Files selected for processing (1)
  • en/docs/next/ai-workspace/about-this-release.md
📝 Walkthrough

Walkthrough

Added the AI Workspace 1.0.0 release page. It documents product capabilities, security, invocation, deployment, authentication, compatibility, and issue references. The page is linked in the next-version AI Workspace navigation.

Changes

AI Workspace 1.0.0 release documentation

Layer / File(s) Summary
Release page and navigation
en/docs/next/ai-workspace/about-this-release.md, en/mkdocs.yml
Added release metadata, product overview, downloads, first-release context, and the navigation entry.
Workspace configuration and proxy capabilities
en/docs/next/ai-workspace/about-this-release.md
Documented workspace configuration, gateway registration, providers, App LLM and MCP proxies, policies, routing, guardrails, rate limiting, and transformations.
Security and invocation workflows
en/docs/next/ai-workspace/about-this-release.md
Documented custom policies, encrypted secrets, secret rotation, SDK invocation, authentication, and gateway artifact synchronization.
Operations and release references
en/docs/next/ai-workspace/about-this-release.md
Documented ap CLI workflows, Moesif telemetry, deployment settings, authentication, compatibility, first-release status, and known issues.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description includes the purpose and issue link but omits most required sections, including goals, approach, testing, security, and documentation details. Complete the required template sections and provide relevant details for goals, approach, checklist items, testing, security checks, documentation, and related impacts.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the main change: adding an About this Release section to AI Workspace documentation.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit 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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 12

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

Inline comments:
In `@en/docs/next/ai-workspace/about-this-release.md`:
- Line 180: Update the “Git-based CI/CD with the ap CLI” heading in the release
documentation so the ap command is enclosed in backticks, preserving the rest of
the heading text unchanged.
- Line 225: Update the sentence following the AI Workspace compatibility
statement to say “The following table lists the product versions tested with
this release.”
- Line 55: Replace the figurative wording in the release notes at the affected
entries with the specified direct terms: use “Support multiple proxies,” “Routes
requests through the gateway,” “Routes requests to several providers,” “Flow
from AI Workspace to the gateway,” and “Stops without generating weaker values,”
while preserving the surrounding content.
- Line 197: Update the Insights page reference in the release notes to format
“Insights” as a bold UI element, matching the existing formatting for other page
names such as Rate Limiting.
- Line 193: Update the Moesif description in the release documentation to remove
the marketing descriptor “AI-native,” leaving the neutral description “an API
analytics platform.”
- Line 173: Update the “Automatic sync” release-note bullet to explicitly state
that automatic sync is enabled by default, replacing the ambiguous “it’s on by
default” phrasing while preserving the listed synced resources.
- Around line 109-110: Update the two rate-limit labels in the release
documentation to use consistent punctuation, replacing the spaced-hyphen format
with the colon format: “Rate limit: basic” and “Rate limit: advanced.”
- Line 17: Split the overlong sentences in “about-this-release.md” at natural
boundaries so every resulting sentence contains fewer than 26 words, including
the sentence around “AI Workspace” and the sentences at the referenced lines.
Preserve the original meaning and readability without changing the documented
content.
- Line 17: Update the release page so every listed abbreviation is expanded at
its first occurrence—Artificial Intelligence (AI), Model Context Protocol (MCP),
Uniform Resource Locator (URL), Generative AI (GenAI), Application Programming
Interface (API), Hypertext Transfer Protocol (HTTP), JavaScript Object Notation
(JSON), United States dollars (USD), User Interface (UI), Software Development
Kit (SDK), Continuous Integration/Continuous Delivery (CI/CD), Command-Line
Interface (CLI), Transport Layer Security (TLS), and JSON Web Token (JWT). Move
the existing Model Context Protocol definition from its later occurrence to the
first use near the page introduction, while preserving the already-defined LLM,
PII, GCRA, and OIDC terminology.
- Line 37: Replace the repeated “Learn more” and “WSO2 API Platform” link labels
throughout the release document with short, unique, destination-specific text,
including distinct labels for each feature overview/setup link and for closed
versus open AI Workspace issue links; keep all existing link targets unchanged.
- Line 34: Rewrite the conditional sentences at the documented release-notes
locations so each begins with its “If…” clause before the consequence, using the
reviewer-provided wording and preserving the existing meaning.
- Around line 15-21: Update the introduction in “About this release” to identify
platform teams and developers as the intended audience. At the first use of each
WSO2-specific term, link it to the existing root-level glossary; if no glossary
exists, add a Glossary section with the required definitions.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b255d0b5-8ef2-4c01-a408-1bc2927686fb

📥 Commits

Reviewing files that changed from the base of the PR and between 63ec24c and ca46c87.

📒 Files selected for processing (2)
  • en/docs/next/ai-workspace/about-this-release.md
  • en/mkdocs.yml

Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
…ease notes and clarify that this is the first release with no prior changes, improvements, or known issues.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

♻️ Duplicate comments (1)
en/docs/next/ai-workspace/about-this-release.md (1)

17-17: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Complete the remaining first-use definitions.

The page still uses these abbreviations before defining them:

  • Line 17: AI in “AI traffic.”
  • Line 56: API.
  • Line 64: URL.
  • Line 88: HTTP.
  • Line 102: JSON.
  • Line 114: USD.
  • Lines 182-184: CI/CD and CLI appear in the heading before their definitions.

Define each term at its first use. Remove the abbreviations from the heading, or expand them in the heading.

As per coding guidelines, define every acronym and initialism at first use.

Also applies to: 56-56, 64-64, 88-88, 102-102, 114-114, 182-184

🤖 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 `@en/docs/next/ai-workspace/about-this-release.md` at line 17, Update the
documentation prose in about-this-release so every listed abbreviation is
expanded or defined at its first occurrence: AI, API, URL, HTTP, JSON, USD,
CI/CD, and CLI. Adjust the heading containing CI/CD and CLI or define both terms
there, while preserving the existing meaning and readability of the page.

Sources: Coding guidelines, Path instructions

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

Inline comments:
In `@en/docs/next/ai-workspace/about-this-release.md`:
- Line 75: Update the sentence near the App LLM proxy description and the
corresponding sentence near line 178 so each begins with its conditional “If”
clause, followed by the consequence, while keeping each sentence under 26 words.
- Line 109: Revise the introductory sentence in the AI Workspace limits section
to avoid claiming that all AI services bill per token; qualify it to say many
services use token-based billing or remove the billing rationale and describe
the supported traffic limits directly.
- Line 68: Update the Versioning description in the release documentation to use
timeless wording: describe the highest-numbered custom-template version rather
than the most recent version, and replace any corresponding “new provider”
wording at the referenced entry with “replacement provider.”

---

Duplicate comments:
In `@en/docs/next/ai-workspace/about-this-release.md`:
- Line 17: Update the documentation prose in about-this-release so every listed
abbreviation is expanded or defined at its first occurrence: AI, API, URL, HTTP,
JSON, USD, CI/CD, and CLI. Adjust the heading containing CI/CD and CLI or define
both terms there, while preserving the existing meaning and readability of the
page.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f92e5e33-3510-437d-8d8f-7340261b8281

📥 Commits

Reviewing files that changed from the base of the PR and between ca46c87 and b45266b.

📒 Files selected for processing (1)
  • en/docs/next/ai-workspace/about-this-release.md

Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
coderabbitai[bot]
coderabbitai Bot previously approved these changes Aug 5, 2026
…mprehensive overview of its capabilities and deployment process.
Comment thread en/docs/next/ai-workspace/about-this-release.md
Krishanx92
Krishanx92 previously approved these changes Aug 6, 2026
@Thushani-Jayasekera

Copy link
Copy Markdown
Contributor Author

@CodeRabbit review

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

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

Inline comments:
In `@en/docs/next/ai-workspace/about-this-release.md`:
- Line 118: Update the release-note bullet describing traffic, prompt, and
provider transformations to use the plural noun “transformations” consistently
with the listed subjects.
- Line 112: In the “Rate limit: advanced” bullet, split the existing quota
description into two sentences, keeping all stated capabilities unchanged and
ensuring each sentence contains fewer than 26 words.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 835ec667-80d2-44c4-aea0-5a1fb518ea40

📥 Commits

Reviewing files that changed from the base of the PR and between b45266b and c25df54.

📒 Files selected for processing (1)
  • en/docs/next/ai-workspace/about-this-release.md

Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
Comment thread en/docs/next/ai-workspace/about-this-release.md Outdated
…s of rate limiting and request transformations.
@Thushani-Jayasekera
Thushani-Jayasekera merged commit 4da76f2 into wso2:main Aug 6, 2026
2 checks passed
This was referenced Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants