You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@addaleax There's still the issue of updating node-core-utils which I think will complain if it doesn't detect a full or lite CI. And probably nodejs/node#29783 should land on 10.x before we delete the pipeline job on the off chance a doc-only PR needs to land on 10.x. (I'll assume we can cope with 8.x with it being so near to End-of-Life.)
I've no preference as to whether nodejs/node#29770 is kept open to track those, or closed and new issues opened for the remainder.
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
Activity
addaleax commentedon Dec 16, 2019
Suggestion: Just formalize nodejs/node#29770 and scrap this job?
richardlau commentedon Dec 16, 2019
It was formalized in nodejs/node#30330?
addaleax commentedon Dec 16, 2019
@richardlau Sorry for the confusion, there was no visible connection between the two on Github :) Can we close nodejs/node#29770 then?
richardlau commentedon Dec 16, 2019
@addaleax There's still the issue of updating
node-core-utilswhich I think will complain if it doesn't detect a full or lite CI. And probably nodejs/node#29783 should land on10.xbefore we delete the pipeline job on the off chance a doc-only PR needs to land on10.x. (I'll assume we can cope with8.xwith it being so near to End-of-Life.)I've no preference as to whether nodejs/node#29770 is kept open to track those, or closed and new issues opened for the remainder.
github-actions commentedon Oct 12, 2020
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.