-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[CI] Use node v14 instead of node v16 untill it will pass again #16595
Conversation
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.
TBH if we're doing this we should really change to 1.14 full stop
hmm can do it ... then just go back to 1.14 until fix |
@zeripath ajusted |
Codecov Report
@@ Coverage Diff @@
## main #16595 +/- ##
==========================================
+ Coverage 45.35% 45.37% +0.01%
==========================================
Files 750 750
Lines 85096 85098 +2
==========================================
+ Hits 38599 38609 +10
+ Misses 40252 40244 -8
Partials 6245 6245
Continue to review full report at Codecov.
|
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.
don't think we use any node 16 feature yet, so this should work.
…itea#16595) * for CI release: use node 14 (lts) to build until 16 do fail * all in for node v14.x
… (#16599) * for CI release: use node 14 (lts) to build until 16 do fail * all in for node v14.x
…itea#16595) * for CI release: use node 14 (lts) to build until 16 do fail * all in for node v14.x
followup of #16591
fix https://drone.gitea.io/go-gitea/gitea/42522/4/3