Skip to content

fix(deps): update node.js versions in examples#897

Merged
mschile merged 2 commits into
cypress-io:masterfrom
MikeMcC399:remove/node-14
May 1, 2023
Merged

fix(deps): update node.js versions in examples#897
mschile merged 2 commits into
cypress-io:masterfrom
MikeMcC399:remove/node-14

Conversation

@MikeMcC399

Copy link
Copy Markdown
Collaborator

Node.js 14 moved into end-of-life status on April 30, 2023 and is therefore no longer officially supported. The versions which are currently supported by Node.js according to their Release schedule are now 16, 18, 19 and 20.

This PR takes account of this Node.js status change and it removes Node.js 14 ...

All examples in the README file which use a matrix of Node.js versions are moved to the consistent set:

```yml
    strategy:
    matrix:
        node: [16, 18, 19, 20]
```

The Node.js Support section is moved to near the bottom of the README file above the section Changelog to which it relates. Some more detail is added to the table concerning when certain Node.js version additions and removals were made.

There is no change to the action itself which continues to use node16 as its running environment, therefore these changes are not breaking changes. node16 is the current latest available version for GitHub JavaScript actions.

(The next status change for Node.js is planned for June 1, 2023, when Node.js 19 enters end-of-life.)

References

remove node.js 14
update changelog table
@MikeMcC399 MikeMcC399 marked this pull request as ready for review May 1, 2023 06:57
@mschile mschile merged commit ecd4b8b into cypress-io:master May 1, 2023
@github-actions

github-actions Bot commented May 1, 2023

Copy link
Copy Markdown

🎉 This PR is included in version 5.6.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@MikeMcC399 MikeMcC399 deleted the remove/node-14 branch May 1, 2023 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants