Update readme

[Krishanx92]

Purpose

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

Goals

Describe what solutions this feature or fix introduces to address the problems outlined above.

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI. 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>

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

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

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

Related PRs

List any other related PRs

Test environment

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: CHILL

Plan: Pro

Run ID: f40d06ba-0ae6-4285-9895-65d96086b8b1

📥 Commits

Reviewing files that changed from the base of the PR and between fba3db7 and 7ded68b.

📒 Files selected for processing (1)

• gateway/build.yaml

📝 Walkthrough

Walkthrough

The gateway snapshot version is updated from 1.2.0-beta-SNAPSHOT to 1.2.0-alpha2-SNAPSHOT.

Changes

Gateway version update

Layer / File(s)	Summary
Update gateway snapshot version gateway/VERSION	The recorded snapshot version changes to 1.2.0-alpha2-SNAPSHOT.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• wso2/api-platform#2635: Updates the same gateway/VERSION snapshot version file.

Suggested reviewers: github-actions[bot], renuka-fernando

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title says "Update readme," but the PR only changes gateway/VERSION, so it is misleading and off-topic.	Rename the title to describe the version bump in gateway/VERSION, such as "Bump gateway version to 1.2.0-alpha2-SNAPSHOT."
Description check	⚠️ Warning	The description is only the template text and contains no filled-in purpose, goals, approach, tests, or related links.	Replace the template with actual PR details for each required section, especially purpose, goals, approach, tests, and documentation.

✅ Passed checks (3 passed)

Check name	Status	Explanation
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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Dependency Validation Results

Dependency name: github.com/gorilla/websocket
Version: v1.5.4-0.20250319132907-e064f32e3674 (was v1.5.3)
Allowed range: >=v1.5.3
Approved: ✅ Yes

Dependency name: golang.org/x/crypto
Version: v0.54.0 (was v0.50.0)
Allowed range: >=v0.31.0
Approved: ✅ Yes

⚠️ Please verify the scope of the dependencies usage is necessary