Skip to content

Conversation

@senthuran16
Copy link
Member

@senthuran16 senthuran16 commented Nov 24, 2025

Purpose

$Subject, after wso2-extensions/apim-km-wso2is#164

Summary by CodeRabbit

  • Chores
    • Upgraded WSO2 Key Manager to version 2.0.9 across all platform modules, including API Control Plane, Gateway, Traffic Manager, and all-in-one APIM configurations. This update ensures consistent versioning across the system and includes stability improvements and bug fixes from the latest Key Manager release.

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

@coderabbitai
Copy link

coderabbitai bot commented Nov 24, 2025

Walkthrough

Version bump of the WSO2 Key Manager dependency (wso2is7.km.version) from 2.0.8 to 2.0.9 across four Maven POM configuration files in the project.

Changes

Cohort / File(s) Summary
WSO2 Key Manager Version Bump
all-in-one-apim/pom.xml, api-control-plane/pom.xml, gateway/pom.xml, traffic-manager/pom.xml
Updated <wso2is7.km.version> property from 2.0.8 to 2.0.9 in each file

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Homogeneous changes across multiple files following an identical pattern
  • No logic modifications, only dependency version updates
  • Straightforward verification of consistency across all POM files

Poem

🐰 A hop and a bump, version neat,
From 2.0.8 to 2.0.9 so sweet!
Key Manager's updated with care,
Across all the configs, everywhere! ✨

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 'Bump IS7 connector version to 2.0.9' clearly and specifically describes the main change across all modified pom.xml files, which is updating the wso2is7.km.version property from 2.0.8 to 2.0.9.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ 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 8cd618c and 3ab8d95.

📒 Files selected for processing (4)
  • all-in-one-apim/pom.xml (1 hunks)
  • api-control-plane/pom.xml (1 hunks)
  • gateway/pom.xml (1 hunks)
  • traffic-manager/pom.xml (1 hunks)
🔇 Additional comments (4)
traffic-manager/pom.xml (1)

1476-1476: Consistent version bump to 2.0.9.
Matches other modules; proceed after upstream availability check passes. Use the script above.

api-control-plane/pom.xml (1)

1476-1476: Aligned with project-wide KM 2.0.9.
No issues spotted; verify no remaining 2.0.8 refs and successful resolution in a dry build.

gateway/pom.xml (1)

1476-1476: Gateway property bump: OK.
Change is straightforward; validate artifact availability and run a quick dependency resolution check.

all-in-one-apim/pom.xml (1)

1497-1497: IS7 KM → 2.0.9: Repo alignment confirmed; upstream availability unconfirmed.

Repo-wide checks passed:

  • ✓ All property definitions are consistently set to 2.0.9 across all pom.xml files
  • ✓ No remaining 2.0.8 references to ${wso2is7.km.version} (2.0.8 hits found are for unrelated dependencies: npm istanbul-lib-report and oro libraries)

However, upstream verification inconclusive:

  • 2.0.9 could not be found in public WSO2 Nexus/Maven indexes
  • Public sources show earlier versions (2.0.5/2.0.x)

Please manually verify that apim-km-wso2is:2.0.9 is available in your WSO2 repository (may be private/internal) and confirm no breaking changes between the previous and 2.0.9 releases.


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 and usage tips.

@senthuran16 senthuran16 merged commit aeebd84 into wso2:master Nov 28, 2025
8 checks passed
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