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
{{ message }}
Repository navigation
Resolve Node.js Buffer() deprecation warning (DEP0005) in workflow runs #331
During PR review of PSModule/NerdFonts#67, the following deprecation warning was detected in CI workflow logs across multiple jobs (Test-Module and Lint-Module on all three platforms — Linux, macOS, Windows):
(node:PID) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues.
Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
This warning originates from the Node.js runtime used by GitHub Actions infrastructure — likely from a dependency of one of the reusable workflows or actions referenced by the Process-PSModule workflow. Since this affects all repositories consuming the shared workflow, the issue belongs here rather than in individual consumer repos.
Impact
Currently a warning only (no functional impact). However, Buffer() without new is a known security concern (potential uninitialized memory exposure) and may eventually become a hard error in future Node.js versions used by GitHub Actions runners.
Investigation needed
Identify which specific action or tool triggers the Buffer() call (use node --trace-deprecation if possible)
Check if updating pinned action versions resolves the warning
The warning appeared in Test-Module and Lint-Module job steps specifically
Also observed during review of PSModule/Jwt#18 in successful Process-PSModule run 25635647976 on 2026-05-10. The warning appeared in Test-Module/Lint-Module, Test-Module/Test-Module, and Test-ModuleLocal/Test-Jwt across Linux, macOS, and Windows.
No Jwt-local fix was applied because the warning comes from the shared Process-PSModule workflow/tooling.
Activity
MariusStorhaug commentedon May 10, 2026
Also observed during review of PSModule/Jwt#18 in successful Process-PSModule run 25635647976 on 2026-05-10. The warning appeared in Test-Module/Lint-Module, Test-Module/Test-Module, and Test-ModuleLocal/Test-Jwt across Linux, macOS, and Windows.
No Jwt-local fix was applied because the warning comes from the shared Process-PSModule workflow/tooling.