Michaël Zasso
Michaël Zasso
@nodejs/documentation I don't know how to handle the conflict about `introduced_in` on the main branch: ``` ======= > 30187baf20 (2022-08-16, Version 16.17.0 'Gallium' (LTS)) ``` I'm going to push with...
Also @nodejs/releasers @MylesBorins note that https://github.com/nodejs/node/releases/tag/v16.17.0 is truncated because GitHub imposes a size limit on the contents.
If `fs` is completely denied, does it block the module loader? For example `require('./package.json')`
> It must be able to restrict access to specific folders and files Don't we actually want the opposite (in common use cases)? It seems way more usual to me...
The documentation for a release is immutable, so there's unfortunately nothing we can do about that. Maybe someone could try to contact GitHub and ask them to redirect those "edit"...
I created a discussion: https://github.com/orgs/community/discussions/28849
If I understand correctly, after https://github.com/nodejs/node/pull/44174 lands, we can close this PR and remove the backport label from https://github.com/nodejs/node/pull/43714 ?
It's more about communicating with browsers, not becoming one.
I'm very reluctant about adding this because I think it's a mistake to resume CI without looking at the failures, and if you are looking at the failures you can...
Was it considered to allow triagers to access the Jenkins feature?