Skip to content

Conversation

@ivanduplenskikh
Copy link
Contributor

@ivanduplenskikh ivanduplenskikh commented Jan 27, 2026

Context

This PR implements Node.js 24 support for all Azure CLI tasks (V1, V2, and V3)
AB#2339106


Task Name

  • AzureCLIV1
  • AzureCLIV2
  • AzureCLIV3

Description

This PR adds Node 24 runtime support to all three versions of the Azure CLI tasks


Risk Assessment (Low / Medium / High)

Medium

Reasoning:

  • Node 24 runtime addition is additive and does not modify existing Node 20 execution handlers
  • Dependencies are updated to versions that maintain backward compatibility
  • No breaking changes to task behavior, inputs, or outputs, but not all cases might be covered
  • Changes follow established patterns for multi-node runtime support in Azure Pipelines tasks

Mitigating Factors:

  • Existing Node 20_1 handlers remain unchanged and operational
  • Node 24 support is standard across Azure Pipelines task ecosystem
  • Task library updates (azure-pipelines-task-lib v5) are designed for forward compatibility

Change Behind Feature Flag (Yes / No)

This change cannot be behind a feature flag


Tech Design / Approach

N


Documentation Changes Required (Yes/No)

N


Unit Tests Added or Updated (Yes / No)

N


Additional Testing Performed

Build Validation:

  • ✅ Successfully built all three tasks with Node 24 configuration using node make.js build
  • ✅ Verified generated artifacts in _generated/AzureCLI{V1,V2,V3}_Node24/
  • ✅ Confirmed dependency resolution with Node 24-compatible package locks

Dependency Audits:

  • ✅ Verified azure-pipelines-task-lib v5.2.4 compatibility with Node 24
  • ✅ Confirmed azure-devops-node-api v15.1.3 supports Node 24
  • ✅ Validated TypeScript 5.7.2 compilation with @types/node v24

Logging Added/Updated (Yes/No)

N


Telemetry Added/Updated (Yes/No)

N


Rollback Scenario and Process (Yes/No)

Rollback Strategy:

  1. Agent-Level Mitigation: If Node 24 runtime issues are discovered, agents can be configured to prefer Node 20 handlers
  2. Task Version Pinning: Users experiencing issues can pin to previous task versions (V1: 1.269.0, V2: 2.269.0, V3: 3.268.1) that only support Node 20
  3. Task override: Task can be overridden with the documented TSG
  4. Code Rollback: Revert this PR and remove Node 24 handlers from task manifests
  5. Dependency Rollback: If library incompatibilities arise, revert dependency updates while retaining Node 20 support

Dependency Impact Assessed and Regression Tested (Yes/No)

N


Checklist

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

@ivanduplenskikh ivanduplenskikh requested review from a team and manolerazvan as code owners January 27, 2026 12:22
@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from 017a8d4 to 3f59cfd Compare January 27, 2026 12:22
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from 3f59cfd to a5e11a4 Compare January 27, 2026 12:53
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from a5e11a4 to 64d525d Compare January 27, 2026 13:23
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch 2 times, most recently from dca887d to 4040931 Compare January 28, 2026 14:17
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@gerschinner

This comment was marked as spam.

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from 4040931 to f069fcb Compare January 28, 2026 15:53
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from f069fcb to cee8894 Compare January 28, 2026 16:22
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from cee8894 to 81cd2f9 Compare January 29, 2026 10:17
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch 2 times, most recently from 9a21616 to 28f763a Compare February 2, 2026 11:17
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from 28f763a to e4bc441 Compare February 2, 2026 15:16
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch 2 times, most recently from 4a9ed72 to 35b0187 Compare February 2, 2026 17:17
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch 3 times, most recently from f125652 to f81fa9f Compare February 4, 2026 11:00
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from 3ee59c0 to 822fdaa Compare February 5, 2026 09:35
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

- Created package.json for Azure CLI V3 task with dependencies and scripts.
- Implemented ScriptType and Utility classes to handle script execution and management.
- Added task.json to define task metadata, inputs, and execution details.
- Included localization support in task.loc.json for user-friendly messages.
- Configured TypeScript compilation settings in tsconfig.json.
- Updated make-options.json to include Azure CLI V3 task for Node 24_1.
@ivanduplenskikh ivanduplenskikh force-pushed the users/iduplenskikh/AzureCLI-node24 branch from 7af707b to 67b063b Compare February 6, 2026 11:31
@ivanduplenskikh
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@ivanduplenskikh ivanduplenskikh merged commit 018d7cf into master Feb 6, 2026
14 checks passed
@ivanduplenskikh ivanduplenskikh deleted the users/iduplenskikh/AzureCLI-node24 branch February 6, 2026 12:16
Deekshitha2812 added a commit that referenced this pull request Feb 9, 2026
Deekshitha2812 added a commit that referenced this pull request Feb 9, 2026
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.

4 participants