Hi, RTL maintainer here.
myNode currently ships RTL v0.15.0 (mynode_app_versions.sh line 128), which was released in December 2023. RTL has published twelve releases since then; the current release is v0.15.12 (2026-09-08). The 0.15.x series carries a long list of bug fixes for LND users, along with some security-related hardening of the authentication and configuration paths, so we would like to see myNode users on a current build. RTL's support policy covers the latest release only.
The comment above the pin notes that moving past v0.15.0 needs a newer Node.js. To be precise about the current requirement:
- RTL v0.15.12 declares
"node": ">=20.19.0" in package.json.
- Node.js 18 reached end-of-life in April 2025, so the
NODE_JS_VERSION="18.x" pin will need to move to 20.x (or later) for any RTL upgrade.
The install recipe otherwise needs only a small update. Releases are still published as signed tarballs with a .tar.gz.asc next to them, and there are no config-format changes for an LND-only setup between v0.15.0 and v0.15.12. The documented install command is now npm ci --omit=dev --legacy-peer-deps (the README used npm install --omit=dev at v0.15.0); npm ci installs exactly what the shipped package-lock.json pins, and --only=production is the deprecated spelling of --omit=dev. Release notes for each version are in the repo under release-notes/.
If bumping the system Node.js is more than you want to take on right now, an alternative is the official Docker image, shahanafarooqui/rtl (https://hub.docker.com/r/shahanafarooqui/rtl), published for every release for linux/amd64, linux/arm64 and linux/arm/v7. It carries its own Node runtime, so RTL's Node requirement stops being tied to the host, and the same RTL-Config.json works unchanged when mounted into the container.
Happy to answer any questions about the version jump. Thanks for shipping RTL all these years.
Hi, RTL maintainer here.
myNode currently ships RTL v0.15.0 (
mynode_app_versions.shline 128), which was released in December 2023. RTL has published twelve releases since then; the current release is v0.15.12 (2026-09-08). The 0.15.x series carries a long list of bug fixes for LND users, along with some security-related hardening of the authentication and configuration paths, so we would like to see myNode users on a current build. RTL's support policy covers the latest release only.The comment above the pin notes that moving past v0.15.0 needs a newer Node.js. To be precise about the current requirement:
"node": ">=20.19.0"inpackage.json.NODE_JS_VERSION="18.x"pin will need to move to 20.x (or later) for any RTL upgrade.The install recipe otherwise needs only a small update. Releases are still published as signed tarballs with a
.tar.gz.ascnext to them, and there are no config-format changes for an LND-only setup between v0.15.0 and v0.15.12. The documented install command is nownpm ci --omit=dev --legacy-peer-deps(the README usednpm install --omit=devat v0.15.0);npm ciinstalls exactly what the shippedpackage-lock.jsonpins, and--only=productionis the deprecated spelling of--omit=dev. Release notes for each version are in the repo underrelease-notes/.If bumping the system Node.js is more than you want to take on right now, an alternative is the official Docker image,
shahanafarooqui/rtl(https://hub.docker.com/r/shahanafarooqui/rtl), published for every release forlinux/amd64,linux/arm64andlinux/arm/v7. It carries its own Node runtime, so RTL's Node requirement stops being tied to the host, and the sameRTL-Config.jsonworks unchanged when mounted into the container.Happy to answer any questions about the version jump. Thanks for shipping RTL all these years.