Closed legobeat closed 1 year ago
Hm, do we want to set .nvmrc
to lts/*
? That's what it is now, but we've often lagged behind a bit.
How about pinning to lts as of now, 18
?
I guess it's mostly a matter of if you want future upgrades to be explicit or not.
Oh, well right now we're still supporting 16, so...?
@haltman-at Note that the value in .nvmrc
does not affect which version unit tests are being run in (which still includes 16
) - only the yarncheck
job is being changed to use .nvmrc
here.
PR description
engines.node
to indicate supported Node.js version range.nvmrc
set tolts/*
yarncheck
job from.nvmrc
instead of using harcoded vesionTesting instructions
Documentation
doc-change-required
label to this PR if documentation updates are required.Breaking changes and new features
breaking-change
andnew-feature
labels for the appropriate packages.