-
Notifications
You must be signed in to change notification settings - Fork 2.7k
KubernetesV1 task Node 24 migration #21714
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+1,049
−261
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- 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.
Contributor
Author
|
/azp run |
|
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.
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s), but failed to run 1 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
nemanjarogic
approved these changes
Jan 28, 2026
Contributor
Author
|
/azp run |
|
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
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