From f15541eb69cf4ca7b918e391d9a30f756761a3df Mon Sep 17 00:00:00 2001 From: Aryan Kumar Date: Mon, 31 Aug 2026 14:54:09 +0530 Subject: [PATCH] feat(cli): warn that the next major will require Node 20+ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Nothing currently tells users the next major release raises the minimum to Node 20. Print a heads up on every run, naming both ways out: pin @percy/cli to its current major, or get the setup onto Node 20+. Warning only. The current major still supports Node 14+, so `engines` stays at ">=14" — that bump belongs to the major release itself. Co-Authored-By: Claude Opus 5 (1M context) --- packages/cli/bin/run.cjs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/packages/cli/bin/run.cjs b/packages/cli/bin/run.cjs index eb657c068..ae28f8f38 100755 --- a/packages/cli/bin/run.cjs +++ b/packages/cli/bin/run.cjs @@ -8,6 +8,11 @@ if (parseInt(process.version.split('.')[0].substring(1), 10) < 14) { process.exit(1); } +// heads up ahead of the next major release, which raises the minimum to Node 20 +console.warn('Heads up! The next major version of @percy/cli will require Node 20+. ' + ( + 'Either pin @percy/cli to its current major version, or make sure your setup runs ' + + 'on Node 20+, before the next major release.')); + import('../dist/index.js') .then(async ({ percy, checkForUpdate }) => { await checkForUpdate();