Skip to content
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

chore(deps): update actions/setup-node action to v3 #2497

Merged
merged 1 commit into from
Feb 25, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 25, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
actions/setup-node action major v2 -> v3

Release Notes

actions/setup-node

v3

Compare Source


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot requested review from Jolg42 and millsp February 25, 2022 08:11
@Jolg42
Copy link
Contributor

Jolg42 commented Feb 25, 2022

https://github.com/actions/setup-node/releases/tag/v3.0.0

In scope of this release we changed version of the runtime Node.js for the setup-node action and updated package-lock.json file to v2.
Breaking Changes
With the update to Node 16 in actions/setup-node#414, all scripts will now be run with Node 16 rather than Node 12.
We removed deprecated version input (actions/setup-node#424). Please use node-version input instead.

@Jolg42 Jolg42 merged commit 95f77e8 into dev Feb 25, 2022
@Jolg42 Jolg42 deleted the renovate/actions-setup-node-3.x branch February 25, 2022 08:53
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