Review requested:

• @nodejs/security-wg

nbytes PR: nodejs/nbytes#12

Third Benchmark CI run, ternary:
https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1792/console

01:03:52                                                 confidence improvement accuracy (*)   (**)  (***)
01:03:52 buffers/buffer-hex-decode.js n=1000000 len=1024        ***    167.49 %       ±1.45% ±1.94% ±2.56%
01:03:52 buffers/buffer-hex-decode.js n=1000000 len=64          ***     49.47 %       ±1.94% ±2.59% ±3.38%
01:03:52 buffers/buffer-hex-encode.js n=1000000 len=1024                 0.15 %       ±0.17% ±0.22% ±0.29%
01:03:52 buffers/buffer-hex-encode.js n=1000000 len=64                   0.06 %       ±0.99% ±1.32% ±1.72%

   ⚠  No approving reviews found
   ✘  Refusing to run CI on potentially unsafe PR

Note: this doesn't bump the version in header, like #61270 didn't bump it from 0.1.1 to 0.1.2

So it's still set there at 0.1.1
That is observable in process.versions.nbytes

Note: this doesn't bump the version in header, like #61270 didn't bump it from 0.1.1 to 0.1.2

So it's still set there at 0.1.1 That is observable in process.versions.nbytes

Did you use tools/dep_updaters/update-nbytes.sh? Honestly I feel like we should only use the bot to update deps, fewer surprises and less work for everyone.

@aduh95 No, I didn't

#61270 is from the bot though and it didn't update the version from 0.1.1 to 0.1.2
Currently main already has 0.1.2 labeled as 0.1.1, I just kept that
Launched through the bot: https://github.com/nodejs/node/actions/runs/22159105153

Superseded by #61879