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

feat: support node v14 #7582

Merged
merged 6 commits into from
Oct 29, 2020
Merged

feat: support node v14 #7582

merged 6 commits into from
Oct 29, 2020

Conversation

viceice
Copy link
Member

@viceice viceice commented Oct 28, 2020

  • build v14 on ci
  • fix ::set-env deprecation
  • do not support node v13 (ended on 2020-06-01)

should we be more strict, eg ^12.13.0 || >=14.15.0 , as 14.15.0 is first v14 lts ?

@CLAassistant
Copy link

CLAassistant commented Oct 28, 2020

CLA assistant check
All committers have signed the CLA.

@rarkins
Copy link
Collaborator

rarkins commented Oct 28, 2020

should we be more strict, eg ^12.13.0 || >=14.15.0 , as 14.15.0 is first v14 lts ?

I think so, because we sometimes depend on features which are added to the major releases prior to LTS, and we have no interest in chasing after pre-LTS versions to work out why something's failing.

@viceice

This comment has been minimized.

@viceice
Copy link
Member Author

viceice commented Oct 28, 2020

should we skip v12 or v14 tests on windows? as we've done with v10 before?

@viceice viceice marked this pull request as ready for review October 28, 2020 08:52
@JamieMagee
Copy link
Contributor

Does this require a major version bump?

@viceice
Copy link
Member Author

viceice commented Oct 28, 2020

Does this require a major version bump?

Why? because we do not support node v13 anymore?

@viceice
Copy link
Member Author

viceice commented Oct 28, 2020

i can split this pr, so we first enable testing v14 only and later change the package.json node requirementes with a major bump, maybe dropping node support <14.15.0

@JamieMagee
Copy link
Contributor

Yeah, it's technically breaking. Though now that I think about it, we drop unsupported versions of GHE without making a major release. This probably falls in the same category.

@rarkins
Copy link
Collaborator

rarkins commented Oct 28, 2020

I don't see why it's a major for us to add v14 support, although if we're taking anything away and it's deserving of a major then we could wait and combine it with others if it's not too inconvenient.

@viceice
Copy link
Member Author

viceice commented Oct 28, 2020

Yeah, it's technically breaking. Though now that I think about it, we drop unsupported versions of GHE without making a major release. This probably falls in the same category.

so yes, i think it's ok to drop unsupported versions with a minor update

I don't see why it's a major for us to add v14 support, although if we're taking anything away and it's deserving of a major then we could wait and combine it with others if it's not too inconvenient.

It's not because adding v14 support, it's because we explicit disallow node ^13 || <14.15

@rarkins rarkins merged commit fdf042b into master Oct 29, 2020
@rarkins rarkins deleted the ci/node-v14 branch October 29, 2020 10:41
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 23.65.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants