redyetidev

> PR is currently blocked from landing by unreliable CI. Is that still the case? Except for the skipped MacOS runner, the CI on this LGTM

@nodejs/tsc per https://github.com/nodejs/Release/issues/1034

> > I'm not a core collaborator, so this is only a suggestion: Shouldn't this become a no-op with --experimental-permission? > > I don't think it's relevant for the permission...

This has been superceded by https://github.com/nodejs/node/issues/50993

> Funny enough this PR's github action got stuck for some reasons and therefore stall action to close the PR never happened. Since this is an oz fellow FWIW https://github.com/nodejs/node/issues/54425

> @RedYetiDev your comment is not really helpful or contain any actionable item. please provide direct suggestions. Sorry! I'll do a review instead. I didn't mean for it to come...

The `policy` label should also be removed from the issue tracker

The TSC had a vote on this, and IIRC this is the plan https://github.com/nodejs/TSC/blob/main/votes/2024-06-25-0.json

Bumping, as I believe the stale issues in the repository are far more than they could be. > We should also be careful about the impact. We don't want everyone...

*(requesting review from previous commenters and reviewers)*