-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Build: add node v17 #15193
Build: add node v17 #15193
Conversation
blocked by gajus/eslint-plugin-jsdoc#791 update: fixed in 72e4b53 |
@@ -43,10 +43,10 @@ jobs: | |||
- name: Install Packages | |||
run: npm install | |||
# TODO(btmills): Remove Node 16 --force branching after releasing v8.0.0 final. | |||
if: ${{ !startswith(matrix.node, '16') }} | |||
if: ${{ !startswith(matrix.node, '16') && !startswith(matrix.node, '17') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment above this line indicates we should be able to remove all checks for Node 16? So we probably don’t need to add Node 17, just remove the Node 16 stuff?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As seen in here, eslint-plugin-jsdoc has not not fully supported eslint v8 yet. We will have to wait it been fixed: gajus/eslint-plugin-jsdoc#791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ x] Other, please explain:
What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
no.