Update package versions in ballerina extensions

[KCSAbeywickrama]

Fixing major issues in Ballerina extension after fixing package version with #1223

• Bumped VSCode engine version to ^1.100.0 in ballerina-extension.
• Updated webpack-dev-server to version 5.2.3 in ballerina-visualizer.
• Upgraded html-to-image to version 1.11.11 in both graphql-design-diagram and persist-layer-diagram.

Summary by CodeRabbit

• Chores
  • Updated VS Code extension engine requirement to support 1.100.0 and later.
  • Upgraded several dependencies across modules (axios, @types/vscode, webpack-dev-server, html-to-image).
• Tests
  • Adjusted end-to-end test setup to target VS Code 1.100.0 (alignment with updated tooling).

[coderabbitai]

Walkthrough

Multiple package.json files updated across workspaces to bump dependency and toolchain version ranges (VS Code engine, @types/vscode, axios, html-to-image, webpack-dev-server). Changes are limited to version strings and test setup commands; no source logic changes were made.

Changes

Cohort / File(s)	Summary
VS Code engine & types workspaces/ballerina/ballerina-extension/package.json, workspaces/ballerina/ballerina-core/package.json	Updated engines.vscode from 1.83.1 to ^1.100.0 and bumped @types/vscode from 1.83.1 to 1.100.0; e2e test setup command updated to target VS Code 1.100.0.
axios version bumps (devDeps / deps) workspaces/api-designer/api-designer-extension/package.json, workspaces/choreo/choreo-extension/package.json, workspaces/mi/mi-extension/package.json, workspaces/ballerina/ballerina-extension/package.json, workspaces/wso2-platform/wso2-platform-extension/package.json	Bumped axios (various modules) from older 1.9.x / 1.12.0 versions to 1.13.5.
html-to-image workspaces/ballerina/graphql-design-diagram/package.json, workspaces/ballerina/persist-layer-diagram/package.json	Bumped html-to-image from 1.10.8 to 1.11.11.
Webpack dev server workspaces/ballerina/ballerina-visualizer/package.json	Updated webpack-dev-server devDependency from 5.2.1 to 5.2.3.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I nibble versions, soft and bright,
Pushing numbers to the light,
Engines, axios, images too,
Small hops forward — tidy view.
No code altered, just a gentle tug of new. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description provides specific version bumps and affected packages, but does not follow the required template structure with Purpose, Goals, Approach, and other sections.	Fill out the template sections including Purpose (reference to issue #1223), Goals, Approach, and other relevant sections like Release note and Documentation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating package versions across ballerina extensions and related packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@workspaces/ballerina/ballerina-extension/package.json`:
- Around line 17-18: Update package.json so the declared VS Code engine
(^1.100.0) is consistent with the types and e2e setup: bump the `@types/vscode`
dependency (the entry named "@types/vscode") to a version that matches 1.100
(e.g., 1.100.x or ^1.100.0) and modify the e2e-test-setup script (the script
named "e2e-test-setup" that downloads a specific VS Code tarball) to pull VS
Code 1.100.x instead of 1.83.1; also search the file for any remaining "1.83.1"
literals and update them to the chosen 1.100.x value so types, local tooling and
tests align with the engines constraint.

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

workspaces/wso2-platform/wso2-platform-extension/package.json (1)

15-15: ⚠️ Potential issue | 🟠 Major

e2e-test-setup still downloads VS Code 1.83.1, which doesn't satisfy the ^1.100.0 engine constraint.

Same issue as in choreo-extension/package.json — the engine is ^1.100.0 (Line 15) but e2e-test-setup (Line 224) pulls VS Code 1.83.1. The extension won't activate in that test environment.

Proposed fix

-    "e2e-test-setup": "npx extest get-vscode -c 1.83.1 && npx extest get-chromedriver -c 1.83.1 && npx extest install-vsix -f $(ls vsix/*.vsix)",
+    "e2e-test-setup": "npx extest get-vscode -c 1.100.0 && npx extest get-chromedriver -c 1.100.0 && npx extest install-vsix -f $(ls vsix/*.vsix)",

Also applies to: 224-224

workspaces/choreo/choreo-extension/package.json (1)

14-14: ⚠️ Potential issue | 🟠 Major

Update e2e-test-setup script to match the ^1.100.0 VS Code engine requirement.

The vscode engine constraint (line 14) and @types/vscode dependency (line 194) are both at version 1.100.0, but the e2e-test-setup script (line 174) still downloads VS Code 1.83.1, creating a version mismatch that will cause the extension to fail activation in the test environment. This fix has already been applied in ballerina-extension/package.json (line 1204).

Proposed fix

-    "e2e-test-setup": "npx extest get-vscode -c 1.83.1 && npx extest get-chromedriver -c 1.83.1 && npx extest install-vsix -f $(ls vsix/*.vsix)",
+    "e2e-test-setup": "npx extest get-vscode -c 1.100.0 && npx extest get-chromedriver -c 1.100.0 && npx extest install-vsix -f $(ls vsix/*.vsix)",

🧹 Nitpick comments (1)

workspaces/ballerina/ballerina-core/package.json (1)

53-55: Pre-existing: Node engine constraint >=0.10.3 <16 is severely outdated.

Node 16 reached EOL in September 2023. This isn't introduced by this PR, but worth addressing soon since the rest of the repo uses much newer Node versions.