Skip to content

Conversation

@v-abhishera
Copy link
Contributor

@v-abhishera v-abhishera commented Jan 19, 2026

Context

This PR upgrades KubernetesV1 tasks to support Node.js 24, ensuring compatibility with the latest Node.js runtime in Azure Pipelines agents


Task Name

KubernetesV1


Description

This PR updates KubernetesV1 tasks to add Node.js 24 support

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

Updated @types/node from ^20.3.1 to ^24.10.0
Updated azure-pipelines-task-lib from ^4.16.0 to ^5.2.4
Updated typescript from 5.1.6 to ^5.7.2
Updated azure-pipelines-tasks-kubernetes-common from ^2.252.0 to ^2.267.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)

Yes


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


Checklist

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

- Replace deprecated fs.Stats constructor with plain object to avoid
  DEP0180 deprecation warning in Node 24
- Fix writeFileSync mock to use flexible path matching instead of
  exact match, resolving path format mismatches across platforms

These changes fix test failures when running under Node 24.
- Update @types/node from ^20.3.1 to ^24.10.0
- Update azure-pipelines-task-lib from ^4.16.0 to ^5.2.4
- Update azure-pipelines-tasks-kubernetes-common from ^2.252.0 to ^2.267.0
- Update typescript from 5.1.6 to ^5.7.2

These dependency updates enable Node 24 runtime support and address
security vulnerabilities in transitive dependencies.
…ndencies

- Remove nested azure-pipelines-tool-lib from kubernetes-common
- Remove nested azure-devops-node-api from kubernetes-common

Prevents singleton conflicts when running with Node 24.
@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

…egistry

Regenerated package-lock.json to resolve dependencies from the correct
Azure DevOps registry (pkgs.dev.azure.com/mseng/PipelineTools) instead
of registry.npmjs.org.

This ensures CI pipeline compatibility and proper dependency resolution.
@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-schhabra
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@v-abhishera v-abhishera marked this pull request as ready for review January 27, 2026 15:08
@v-abhishera v-abhishera requested review from a team and manolerazvan as code owners January 27, 2026 15:08
@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s), but failed to run 1 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@v-abhishera v-abhishera merged commit 2f1b5cd into master Jan 28, 2026
14 checks passed
@v-abhishera v-abhishera deleted the users/v-abhishera/KubernetesV1Node24 branch January 28, 2026 09:10
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