fix(ci): simplify Node.js setup by removing matrix strategy#17414
Open
dkamburov wants to merge 1 commit into
Open
fix(ci): simplify Node.js setup by removing matrix strategy#17414dkamburov wants to merge 1 commit into
dkamburov wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Simplifies the Node.js CI workflow by removing the (single-entry) matrix strategy and pinning the job to a fixed Node 22.x setup, reducing YAML complexity while keeping the same runtime version.
Changes:
- Removed the
strategy.matrixblock that only contained22.x. - Updated the setup-node step to use a fixed
node-version: 22.xand adjusted the step name accordingly.
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
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.
Fix the stuck pending check, by removing the matrix to match the rulesets
Closes #
Description
Motivation / Context
Type of Change (check all that apply):
Component(s) / Area(s) Affected:
How Has This Been Tested?
Test Configuration:
Screenshots / Recordings
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)