MsBuildV1 Task node24 Upgrade

[Deekshitha2812]

Context

Updating the task with node24.
📌 AB#2339370

---

Task Name

MsBuildV1

---

Description

Updates the task execution handlers (Node24 handler is added), types@node version is updated to 24.10.0 ,task-lib and type-script version are also updated to 5.2.1 and 5.7.2.

---

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).

---

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Unit Tests Added or Updated ( No)

Indicate whether unit tests were added or modified to reflect these changes.

---

Additional Testing Performed

Manual testing is done. Unit tests are passing. Uploaded to personal org and tested.
https://dev.azure.com/madalas/first_project/_build/results?buildId=529&view=logs&s=96ac2280-8cb4-5df5-99de-dd2da759617d

---

Logging Added/Updated (No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[Deekshitha2812]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Deekshitha2812]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Deekshitha2812]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Deekshitha2812]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Deekshitha2812]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).