Back to Changelog
Panel Backend
v1.0.467
Node.js and Python runtimes that cannot start are now caught, repaired and reported instead of being listed as working.
Improvements
3- Node.js versions now carry their real support state, read from the Node project's own release schedule: current, LTS, maintenance or end of life. Six of the nine versions on offer were in fact end of life, including Node 20, and all of them were labelled "Current".
- Python series carry the same information, derived from CPython's published five-year cycle: actively supported, security fixes only, or end of life.
- An operator can choose which installed version is the default rather than having the newest install silently take that role. For Node.js the choice also decides what a login shell resolves; for Python nothing is placed on the system PATH, because a pool python3 in front of the system one would be picked up by every script on the machine.
Bug Fixes
2- A Node.js version could install successfully and still be unable to run. Upstream builds link what upstream had: Node 25 and 26 need libatomic, which Debian and Ubuntu ship by default and the RHEL family does not. Measured on real machines, Node 26 failed to start on AlmaLinux 9 and 10 and on Rocky 9 and 10, while the panel reported it as installed - so an app created against it died on start. Installing now runs the binary before calling it installed, installs the missing library if that is all that stands in the way, and removes the half-installed tree if it still cannot start.
- Servers that already carry such a version are repaired at boot: each installed runtime is run once, and a missing library is installed once. A runtime that already works is left alone and the package manager is never touched.