Add WSO2.wso2-platform extension dependency to ballerina-extension (release/bi-1.8.x)

[Copilot]

Purpose

WSO2.wso2-platform is declared as an extensionDependency on main but is missing from the ballerina-extension on the release/bi-1.8.x branch, meaning VS Code will not auto-install it alongside the Ballerina extension on that release line.

Goals

Ensure WSO2.wso2-platform is listed as an extension dependency in ballerina-extension on release/bi-1.8.x, matching the main branch behaviour.

Approach

Single-line addition to extensionDependencies in workspaces/ballerina/ballerina-extension/package.json:

"extensionDependencies": [
    "anweber.httpbook",
    "WSO2.wso2-platform"
],

UI Component Development

N/A — no UI changes.

• Added reusable UI components to the ui-toolkit. Follow the intructions when adding the componenent.
• Use ui-toolkit components wherever possible. Run npm run storybook from the root directory to view current components.
• Matches with the native VSCode look and feel.

Manage Icons

N/A — no icon changes.

• Added Icons to the font-wso2-vscode. Follow the instructions.

User stories

Users installing the Ballerina extension on VS Code from the release/bi-1.8.x release line will have WSO2.wso2-platform automatically installed as a dependency.

Release note

WSO2.wso2-platform is now declared as a required extension dependency of the Ballerina extension on the 1.8.x release line.

Documentation

N/A — metadata-only change with no user-facing documentation impact.

Training

N/A

Certification

N/A

Marketing

N/A

Automation tests

• Unit tests: N/A
• Integration tests: N/A — package.json metadata change only.

Security checks

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

Samples

N/A

Related PRs

The equivalent change on main was already merged prior to this backport.

Migrations (if applicable)

N/A

Test environment

N/A — package manifest change only.

Learning

N/A

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[xlight05]

@copilot the branch you selected is wrong, change it to 1.8x. branch when making the pr

[Copilot]

@copilot the branch you selected is wrong, change it to 1.8x. branch when making the pr

The code change is correct — WSO2.wso2-platform added to extensionDependencies in workspaces/ballerina/ballerina-extension/package.json on top of release/bi-1.8.x (local commit 6940f0b4). Unfortunately the automated push tool cannot force-push this because the current PR branch on GitHub is based on main (which has diverged thousands of commits from release/bi-1.8.x), causing an unresolvable rebase every time it tries.

The fix needed is very small — could you either:

1. Close this PR and open a new one targeting release/bi-1.8.x with just this diff:

   -    "extensionDependencies": ["anweber.httpbook"],
   +    "extensionDependencies": ["anweber.httpbook", "WSO2.wso2-platform"],

   in workspaces/ballerina/ballerina-extension/package.json, or
2. Force-push the local branch: git push --force origin copilot/add-wso2-wso2-platform-dependency from a checkout at release/bi-1.8.x + that change, then retarget the PR to release/bi-1.8.x.