1001673: Resolved Github dependabot issue for different editing modes in angular gantt chart

[DhineshSF]

Bug description

1001673 : Resolved Github dependabot issue for expand state mapping with remote data in angular gantt chart.

Root cause

The Dependabot alert was triggered because the sample was using an outdated and vulnerable Angular version (~13.3.0) that is no longer supported and has no available patch for recent security vulnerabilities (including CVE-2025-66412 in @angular/compiler and related core packages).

Solution description

Resolved the reported error by updating both angular common/compiler version in package.json file.

Reason for not identifying earlier

• Guidelines not followed. If yes, provide which guideline is not followed.
• Guidelines not given. If yes, provide which/who need to address.
     Tag label update-guideline-coreteam or update-guideline-productteam.
• If any other reason, provide the details here.

Areas tested against this fix

1. Checked sample works properly.

•   Tested against feature matrix. Feature matrix link
•   NA

Is it a breaking issue?

•   Yes, Tag breaking-issue.
•   NO

If yes, provide the breaking commit details / MR here.

Action taken

Assigned to testing team.

Feature matrix document updated

•   Yes
•   NO
•   NA

Automation details - Mark Is Automated field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the bug is automated.

• BUnit, share corresponding MR.
• E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.
• NA

If the same issue is reproduced in ej2, what will you do?

•   Resolved. Provide MR link.
•   NO. Created task to track it. Share task link.
•   NA

Is this common issue need to be addressed in the same component or on other components in our platform?

•   Yes - Need to check in other components, tag needs-attention-coreteam
•   No

Output screenshots

NA

Blazor Checklist

Confirm whether this feature is ensured in both Blazor Server and WASM

•   NA
•   Yes
•   NO

Is there any new API or existing API name change?

•   Yes. If yes, Provide API Review task link.
•   NO

Is there any existing behavior change due to this code change?

•   Yes. Add breaking-change label.
•   NO

Do the code changes cause any memory leak and performance issue? (Test only if you suspect that your code may cause problem)

•   Yes
•   NO

Reviewer Checklist

•   All provided information are reviewed and ensured.