Context
During PR review of #67, the following deprecation warning was detected in CI workflow logs across multiple jobs (Test-Module and Lint-Module on all three platforms):
(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.
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)
- If the source is in a shared reusable workflow (e.g.,
Process-PSModule), the fix may need to be applied upstream
- If the source is a pinned action version, updating to a newer version may resolve it
Context
During PR review of #67, the following deprecation warning was detected in CI workflow logs across multiple jobs (Test-Module and Lint-Module on all three platforms):
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-PSModuleworkflow.Impact
Currently a warning only (no functional impact). However,
Buffer()withoutnewis 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
Buffer()call (usenode --trace-deprecationif possible)Process-PSModule), the fix may need to be applied upstream