Skip to content

Update node version to latest node 20 and node 24#21813

Open
sanjays-ms wants to merge 3 commits intomasterfrom
users/v-sanjayse/update-node-versions
Open

Update node version to latest node 20 and node 24#21813
sanjays-ms wants to merge 3 commits intomasterfrom
users/v-sanjayse/update-node-versions

Conversation

@sanjays-ms
Copy link
Contributor

@sanjays-ms sanjays-ms commented Feb 10, 2026

Context

AB#2361731

Fixing node vulnerabilities by updating to latest minor version of node 20 and node 24


Task Name

NA - not a task change.


Description

Few packages which are part of the node zip we download and add to the path while building the tasks is marked as vulnerable.

To fix this we are updating the node version being used.

Example Node 24 updates tar version to 7.5.7
Ticket can be resolved once new version is updated


Risk Assessment (Low / Medium / High)

Low - updates only to minor version of node 20 and node 24 no task functionality changes


Change Behind Feature Flag (Yes / No)

No - Not a feature or functionality change


Tech Design / Approach

  • Design has been written and reviewed.
  • Any architectural decisions, trade-offs, and alternatives are captured.

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

  • User guides, API specs, system diagrams, or runbooks are updated.

Unit Tests Added or Updated (Yes / No)

NA


Additional Testing Performed

NA


Logging Added/Updated (Yes/No)

  • Appropriate log statements are added with meaningful messages.
  • Logging does not expose sensitive data.
  • Log levels are used correctly (e.g., info, warn, error).

Telemetry Added/Updated (Yes/No)

  • Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
  • Events are tagged with proper metadata for filtering and analysis.
  • Telemetry is validated in staging or test environments.

Rollback Scenario and Process (Yes/No)

  • Rollback plan is documented.

Dependency Impact Assessed and Regression Tested (Yes/No)

  • All impacted internal modules, APIs, services, and third-party libraries are analyzed.
  • Results are reviewed and confirmed to not break existing functionality.

Checklist

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

@sanjays-ms
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@sanjays-ms
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@sanjays-ms sanjays-ms marked this pull request as ready for review February 26, 2026 13:11
@sanjays-ms sanjays-ms requested review from a team and tarunramsinghani as code owners February 26, 2026 13:11
- task: UseNode@1
displayName: Use node 20
inputs:
versionSpec: 20.x
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will already use the latest as 20.x ??

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