Breaking changes from v2 to v3
See original GitHub issueHi, sorry if I’m not the following the issue format as this is not really an issue rather a question.
If I have a project that uses a beta v2 version
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2.1.0
with:
node-version: 16.x
- run: npm ci
- run: npm test
and decided to update it to v3…
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v3
with:
node-version: 16
- run: npm ci
- run: npm test
would there be breaking changes? Thanks!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Migrating from 2.x to 3.0 - Socket.IO
TL;DR: due to several breaking changes, a v2 client will not be able to connect to a v3 server (and vice versa). Update:...
Read more >Migrating from v2 to v3 - Gatsby
This section explains breaking changes that were made for Gatsby v3. Most, if not all, of those changes had a deprecation message in...
Read more >please highlight breaking changes when migrating from v2 to ...
Actually, I'd like to highlight a breaking change. When using devtools , the set function which saves the partial object to the state...
Read more >To v2 or v3 from v1 - webpack
ExtractTextWebpackPlugin - breaking change. ExtractTextPlugin requires version 2 to work with webpack 2. npm install --save-dev extract-text-webpack-plugin.
Read more >Breaking Changes - Vue 3 Migration Guide
This page lists all Vue 3 breaking changes from Vue 2. While it looks like a lot has changed, a lot of what...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello @walmartwarlord. In v3 we changed the runtime version from node12 to node16. I think it should work as expected.
node-version
input, so basically will it be possible to setup node 14 version. But thinking about it I guess this is what this action about and it is possible to setup any version, while runtime version is only relevant forsetup-node
action itself