upgrade to node 16 #7724
Merged
upgrade to node 16 #7724
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
github-actions
bot
added
area/documentation
alafanechere
approved these changes
Nov 8, 2021
|
Artem confirmed this is fine on Slack. |
schlattk
pushed a commit
to schlattk/airbyte
that referenced
this pull request
Jan 4, 2022
* upgrade to node 16 * does upgrading fontawesome prevent errors
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.
It'd be nice to be on the latest active LTS.
It seems like upgrading Node 16 causes a failure during
npm installwhere we get a 401 for Font Awesome. @jamakase any ideas why this is happening?EDIT: it looks like this is working after upgrading fontawesome. I don't know why.
Also, is the new lock file version ok for us to switch to like this?