Skip to content

Conversation

@v-schhabra
Copy link
Contributor

@v-schhabra v-schhabra commented Jan 30, 2026

Context

This PR upgrades the HelmDeployV0 and HelmDeployV1 task to support Node.js 24, ensuring compatibility with the latest Node.js runtime in Azure Pipelines agents


Task Name

HelmDeployV0 and HelmDeployV1


Description

This PR updates the HelmDeployV0 and HelmDeployV1 task to add Node.js 24 support. Key changes include:

Node.js 24 Runtime Support: Added Node24 execution handler to task.json and task.loc.json
Dependency Updates For HelmDeploV0:

  • Updated @types/node from ^20.3.1 to ^24.10.4
  • Updated azure-pipelines-task-lib from ^4.11.0 to ^5.2.4
  • Updated azure-pipelines-tasks-securefiles-common from ^2.263.0 to ^2.270.0
  • Updated typescript from 5.1.6 to ^5.7.2
  • Updated azure-pipelines-tasks-azure-arm-rest from ^3.267.1 to ^3.270.0
  • Updated azure-pipelines-tasks-docker-common from 2.265.0 to ^2.268.0
  • Updated azure-pipelines-tasks-kubernetes-common ^2.224.1 from to ^2.267.0
  • Updated azure-pipelines-tasks-securefiles-common from ^2.263.0 to ^2.270.0
  • Updated azure-pipelines-tasks-utility-common from 3.267.0to 3.270.0

Dependency Updates For HelmDeploV1:

  • Updated @types/node from ^20.3.1 to ^24.10.4
  • Updated azure-pipelines-task-lib from ^4.13.0 to ^5.2.4
  • Updated typescript from 5.1.6 to ^5.7.2
  • Updated azure-pipelines-tasks-azure-arm-rest from ^3.267.1 to ^3.270.0
  • Updated azure-pipelines-tasks-docker-common from ^2.265.0 to ^2.268.0
  • Updated azure-pipelines-tasks-kubernetes-common ^2.224.1 from to ^2.267.0
  • Updated azure-pipelines-tasks-securefiles-common from ^2.263.0 to ^2.270.0
  • Updated azure-pipelines-tasks-utility-common from 3.267.0 to 3.270.0

Risk Assessment (Low / Medium / High)

Medium

Reasoning:

  • Scope: Changes affect core dependencies including task library and Node.js types
  • Impact: The task is updated up to Node 24
  • 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)

No

This change cannot be behind a feature flag because:

  • The Node24 handler is additive and can't be covered with a feature flag

Tech Design / Approach

No


Documentation Changes Required (Yes/No)

No


Unit Tests Added or Updated (Yes / No)

No


Additional Testing Performed

  • Build verification: Ensure task builds successfully with updated dependencies
  • Runtime testing: Verify task executes correctly on Node.js 24 runtime (on self-hosted agent v4.266.2)
  • Backward compatibility: Confirm task still works with Node20_1 handler

Logging Added/Updated (Yes/No)

No


Telemetry Added/Updated (Yes/No)

No


Rollback Scenario and Process (Yes/No)

Yes

Rollback Plan:

  • Revert commits on this branch
  • Deploy a task fix

or

Mitigation:

  • Override a task version

Dependency Impact Assessed and Regression Tested (Yes/No)

Yes

Impact Assessment:

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


Checklist

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

@v-schhabra v-schhabra marked this pull request as ready for review February 3, 2026 17:14
@v-schhabra v-schhabra requested review from a team and manolerazvan as code owners February 3, 2026 17:14
@v-schhabra
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-schhabra
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-schhabra
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-schhabra
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-gayatrij
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-schhabra
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-schhabra
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.

4 participants