-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[release/5.0] Resolve Component Governance bugs #40218
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
Conversation
|
Hi @wtgodbe. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
|
👀 |
dougbu
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine but please don't merge w/o signoff from someone deeper in our node, npm / yarn world.
| displayName: Install Node 14.x | ||
| inputs: | ||
| versionSpec: 10.x | ||
| versionSpec: 14.x |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we jump all the way forward to 16.x and catch up w/ 'main'❔ Thoughts @javiercn @BrennanConroy…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did this to match 6.0:
aspnetcore/.azure/pipelines/jobs/default-build.yml
Lines 169 to 173 in d5d2e4d
| - ${{ if eq(parameters.installNodeJs, 'true') }}: | |
| - task: NodeTool@0 | |
| displayName: Install Node 14.x | |
| inputs: | |
| versionSpec: 14.x |
Part of #37889. Resolves the remaining High/Critical 5.0 CompGov bug(s)