v7.0.1
Fixed 5
- Fix Python and other non-Node interpreter regression on Ubuntu where bun runtime detection used naive substring matching that incorrectly matched paths containing 'bun', causing routing through ProcessContainerForkBun.js and SyntaxError when Python tried to parse the JS container
- Display max_memory_restart in pm2 describe output when set
- Add missing port option to StartOptions TypeScript declaration
- Fix incorrect file permissions on openrc.tpl template
- Fix Windows cmd.exe regression by reverting bin/pm2 launchers to #!/usr/bin/env node shebang to restore compatibility with npm's pm2.cmd shim
From pm2
7.0.1
Bug Fixes
- Fix Python (and other non-Node) interpreter regression on Ubuntu: bun runtime detection used a naive
includes('bun')substring check that matched any path containing the letters "bun" — most notably/home/ubuntu/.... Affected paths were routed throughProcessContainerForkBun.jsand crashed withSyntaxError: unterminated string literalwhen Python tried to parse the JS container. Anchored the match to the end of the interpreter path (=== 'bun'or/bun$/) in bothlib/God/ForkMode.jsandlib/Common.js#5990 - Display
max_memory_restartinpm2 describeoutput when set #5925 - Add missing
portoption toStartOptionsTypeScript declaration #6045 - Fix incorrect file permissions on
openrc.tpltemplate (0755 → 0644) #5957 - Fix Windows cmd.exe regression: revert
bin/pm2*launchers to#!/usr/bin/env nodeshebang (was polyglot#!/bin/sh). Polyglot worked on Linux/macOS but broke npm'spm2.cmdshim on Windows —cmd.execan't interpret/bin/shshebang and failed with'"/bin/sh"' is not recognized as an internal or external command. PowerShell's auto-generatedpm2.ps1shim happened to callnodedirectly so it kept working, masking the regression. Bun-only Linux/macOS users (no Node installed) need to symlinknodetobun(sudo ln -s $(which bun) /usr/local/bin/node) — same workaround used in the project's bun test Dockerfile. Documented in README #6108