📣 Heads-up: Lightdash is moving to Node.js 24 — Wednesday 29 July 2026 TL;DR — most customers don't need to do anything. Lightdash Cloud and standard Docker self-hosting upgrade automatically. Anyone using the Lightdash CLI — on their local machine or in CI/CD — will need to take action. We're giving about a month's notice so you can schedule it. What's changing On Wednesday 29 July 2026, Lightdash moves to Node.js 24 (the current Active LTS). We're moving off Node.js 20, which reached end-of-life in April 2026, to stay current on security patches, performance, and long-term support. On the day, we'll also publish the exact Lightdash version that requires Node.js 24 and update our GitHub Action templates. What you need to do ☁️ Lightdash Cloud — Nothing. We manage the runtime and roll it out for you, with no downtime or action needed. 🐳 Self-hosted — standard Docker / Helm — Nothing beyond your usual upgrade. From 29 July, the Lightdash image ships with Node.js 24 built in; pull the version we announce that day and deploy as normal. 🛠️ Self-hosted — custom images, modified deployments, or building from source — Please verify your environment on Node.js 24 before 29 July. A base-image bump can pull in other toolchain updates, so it's worth checking ahead of time rather than on the day. ⌨️ Lightdash CLI users — From 29 July, the CLI will require Node.js 24, whether you run it on your local machine or in CI/CD. There's nothing you need to change before then — this notice is just so you can plan it in. When the change lands (we'll confirm the exact version that day), you'll need to be on Node.js 24: • Locally: upgrade your machine to Node.js 24 (e.g. via nvm, fnm, or nodejs.org). • In CI/CD: run your CLI steps on Node 24 — e.g. actions/setup-node with node-version: 24 (also becoming the GitHub-hosted default). If you use our GitHub Action templates, pull the latest — we'll update them for Node 24 on 29 July. • Either way, you can skip managing Node entirely with our standalone CLI binaries, which bundle their own runtime. A note on currency formatting (COP & HUF only) Node.js 24 ships updated international formatting data (ICU/CLDR). As a result, Colombian peso (COP) and Hungarian forint (HUF) amounts in server-generated exports and scheduled deliveries (CSV/Excel, emailed/Slack reports) will display without decimal places — e.g. "COP 1,235" instead of "COP 1,234.50". This matches the current international standard for these currencies and how modern browsers already display them. No other currencies or formats change. If your COP/HUF reports feed downstream automation that expects two decimals, please adjust before the upgrade. Questions? Reply to this thread — we're happy to help with CLI or self-hosting upgrades.