docs: prune out-date node version in favor of LTS #9031
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
prune out-date node version in favor of LTS
Security / Scaling / Testing Considerations
n/a
Documentation / Testing / Upgrade Considerations
I think "we support node LTS" is our goal. Due to issues such as #8599, docs on Platform Requirements currently cite v18.16.0 specifically. In that case, @kbennett2000 regularly tests the getting started docs to be sure it works. I don't think we have a corresponding maintenance trigger for CONTRIBUTING, so "LTS" is probably better.
ci tests 18.x and 20.x, which are the 2 current LTS versions according to the node release schedule:
-- https://github.com/Agoric/agoric-sdk/blob/master/.github/workflows/test-all-packages.yml