Context

Node24 migration
📌 AB#2340631

Task Name

MavenV4.

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.4 and 5.7.2.
The task is build by using --BypassNpmudit.
The node make.js test --task MavenV4 is failed with error.

AssertionError [ERR_ASSERTION]: should not have written to stderr=(node:78088) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

      + expected - actual

      -false
      +true

      at Context.<anonymous> (C:\azure-pipelines-tasks\_build\Tasks\MavenV4\Tests\L0.js:149:13)
      at Generator.next (<anonymous>)
      at fulfilled (C:\azure-pipelines-tasks\_build\Tasks\MavenV4\Tests\L0.js:5:58)
      how to solve this error

this because of url.parse() API deprecation in node24 - Deprecated APIs | Node.js v24.12.0 Documentation.
updated the url.parse() with URL()

Risk Assessment (Low / Medium / High)

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

Change Behind Feature Flag ( 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 (Yes / No)

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

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

Logging Added/Updated (Yes/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 (Yes/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/No)

• 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