Skip to content

Update change log - #414

Merged
Krishanx92 merged 1 commit into
wso2:mainfrom
Krishanx92:self-hosted
Aug 6, 2026
Merged

Update change log#414
Krishanx92 merged 1 commit into
wso2:mainfrom
Krishanx92:self-hosted

Conversation

@Krishanx92

Copy link
Copy Markdown
Contributor

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Checklist

  • Verified that llms.txt (located at en/docs/llms.txt) is updated for AI readiness content.
  • Ensured meaningful alt text for images and that the information contained in an image also appears in text so the relevant info exists in the body of the document.
  • Added or updated frontmatter for the respective pages.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

  • Unit tests

    Code coverage information

  • Integration tests

    Details about the test cases and coverage

Security checks

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Changes

Gateway release documentation

Layer / File(s) Summary
AI Gateway release notes
en/docs/ai-gateway/next/about-this-release.md
Added the AI Gateway 1.1.1 changelog, including new features, configuration changes, behavioral changes, and fixes.
API Gateway release notes
en/docs/api-gateway/next/about-this-release.md
Added the API Gateway 1.2.0 changelog, including new features, configuration changes, behavioral changes, and fixes.
Release page navigation
en/mkdocs.yml
Added navigation entries for both next-version release pages.

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

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description contains only the repository template and provides no purpose, goals, approach, testing, or release details. Complete the required sections with the change-log purpose, implementation details, documentation impact, testing information, and relevant release details.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately identifies the primary change, which is updating the API Gateway and AI Gateway changelogs.
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: 6

🤖 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/ai-gateway/next/about-this-release.md`:
- Line 1: Use sentence case for the headings in both release pages: in
en/docs/ai-gateway/next/about-this-release.md, change “AI Gateway Changelog” to
“AI Gateway changelog” and “Config Changes” to “Config changes”; make the same
heading changes in en/docs/api-gateway/next/about-this-release.md, changing “API
Gateway Changelog” to “API Gateway changelog”.
- Line 1: Both release pages, en/docs/ai-gateway/next/about-this-release.md:1-1
and en/docs/api-gateway/next/about-this-release.md:1-1, need frontmatter
inserted before the H1. Add title, description, canonical_url, md_url, tags,
author or authors, last_updated, and content_type to each page, preserving the
existing release heading and content.
- Line 6: Fix the heading hierarchy in both
en/docs/ai-gateway/next/about-this-release.md:6-6 and
en/docs/api-gateway/next/about-this-release.md:6-6 by changing main section
headings such as “New feature additions” to H2 and keeping “New policies” as H3
beneath them.
- Line 20: Remove the unmatched trailing colon after the AWS authentication link
in both en/docs/ai-gateway/next/about-this-release.md (lines 20-20) and
en/docs/api-gateway/next/about-this-release.md (lines 20-20); no description is
being added.
- Line 10: Update both en/docs/ai-gateway/next/about-this-release.md:10-10 and
en/docs/api-gateway/next/about-this-release.md:10-10 to define or glossary-link
MSSQL, AWS, MCP, LLM, IDP, REST, gRPC, APIP_*, and xDS at first use, linking
WSO2-specific terms to the root glossary.
- Line 12: Resolve the contradictory upstreamDefinitions documentation by
verifying the runtime behavior, then update the release-note entry in both
en/docs/ai-gateway/next/about-this-release.md and
en/docs/api-gateway/next/about-this-release.md at line 12 to consistently state
whether query strings and path fragments are supported or rejected.
🪄 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: e76d82fe-328c-406e-948e-b4570ac734b1

📥 Commits

Reviewing files that changed from the base of the PR and between 4da76f2 and aa12674.

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

Comment thread en/docs/ai-gateway/next/about-this-release.md
Comment thread en/docs/ai-gateway/next/about-this-release.md
Comment thread en/docs/ai-gateway/next/about-this-release.md
Comment thread en/docs/ai-gateway/next/about-this-release.md
Comment thread en/docs/ai-gateway/next/about-this-release.md
@Krishanx92
Krishanx92 merged commit c86b6b4 into wso2:main Aug 6, 2026
2 checks passed
This was referenced Aug 7, 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