Skip to content

Conversation

@AlexVTor
Copy link
Contributor

Context

Migrate the version of node being used for the tasks. Npm audit was also used to update vulnerabilities within the tasks' dependencies.
AB#{2341818}


Task Name

NuGetCommandV2, NpmV1, UniversalPackagesV0


Description

Migrate tasks' node version from node 20 to node 24


Risk Assessment (Low / Medium / High)

Medium

Reasoning:

Scope: Changes affect core dependencies including task library and Node.js types
Backward Compatibility: Full backward compatibility maintained through override

The risk is mitigated by:
Maintaining Node20_1 support alongside Node24 (with override process)
No changes to task logic or functionality


Change Behind Feature Flag (Yes / No)

N - The migration to node 24 cannot be controlled via feature flag


Tech Design / Approach

Design Document


Documentation Changes Required (Yes/No)

N/A


Unit Tests Added or Updated (Yes / No)

L0s were updated to remove dependencies on vulnerable packages


Additional Testing Performed

Manual via devfabric, Automated via l0s and pipelines


Logging Added/Updated (Yes/No)

N


Telemetry Added/Updated (Yes/No)

No


Rollback Scenario and Process (Yes/No)

Rollback Process


Dependency Impact Assessed and Regression Tested (Yes/No)

Updates to the following packages were validated

@types/node v24.10.4 provides accurate type definitions for Node.js 24
azure-pipelines-task-lib v5.2.4 is stable and widely tested
typescript v5.7.2 is the latest stable version with Node.js 24 support


Checklist

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

@AlexVTor AlexVTor requested a review from a team as a code owner January 26, 2026 19:30
@AlexVTor
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@AlexVTor
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants