Michaël Zasso comments

Results 1686 comments of


                                            Michaël Zasso

Creating a branch rule for non LTS staging branches

I mean the staging branch for Current. I found it easier to continuously cherry-pick from main rather than doing everything just before the release proposal. For LTS, I also did...

Creating a branch rule for non LTS staging branches

Now I understand why the checkbox says "above" ![CleanShot 2024-04-30 at 07 14 23@2x](https://github.com/nodejs/Release/assets/2352663/386e8a93-9012-4442-99f8-96a2e64dce9c)

Creating a branch rule for non LTS staging branches

If rulesets are not affected by this limitation, we should migrate asap

Creating a branch rule for non LTS staging branches

What about that: - [Protect LTS staging branches](https://github.com/nodejs/node/settings/rules/714659) - [Protect non-LTS staging branches](https://github.com/nodejs/node/settings/rules/714664)

Creating a branch rule for non LTS staging branches

I can try to migrate the protection of very old branches to a single Ruleset.

Creating a branch rule for non LTS staging branches

https://github.com/nodejs/node/settings/rules/3602466

Consider removing unencrypted rsync server

Something to consider with R2 is that it doesn't contain the symlinks, so it cannot be used alone to make a mirror.

Can we supress the new experimental warning from the new default require(esm) setting?

You can use [`node --no-deprecation`](https://nodejs.org/docs/latest/api/cli.html#--no-deprecation) or `export NODE_OPTIONS="--no-deprecation"`.

Can we supress the new experimental warning from the new default require(esm) setting?

Or disable `require('esm')` with `--no-experimental-require-module`

Can we supress the new experimental warning from the new default require(esm) setting?

I don't know much about Windows, sorry.