From the ChangeLog:

In scope of this release, we update node version runtime from node16 to node20 (actions/setup-python#772). Besides, we update dependencies to the latest versions.

From the ChangeLog:

In scope of this release, we update node version runtime from node16 to node20 (actions/setup-python#772). Besides, we update dependencies to the latest versions.

There's nothing to worry about. JavaScript actions run directly on the runner, and these have a node version in them. (That's why JavaScript actions can be so fast, they just run on the runner without having to install anything on, and can run on all OSes
that github runners support).

Node 20 has been used since October in this very repo since October, when actions/checkout v4 was used.

Node 16 is already EOL, but GitHub managed to start the transition a bit late. They completely skipped node18 (since it is already near the end). (before node 16, javascript actions were run with node 12, and action using node 12 were forced to used node 16 at some point after the transition).

There is nothing "new" added to our workflows. When they say dependencies, it is node/javascript dependencies that are used for that very action.

If you want to wait for me to see if in the megalinter repo I maintain there's any impact, you could, but it is simply a standard action to install software, so I have a high confidence.

The same goes for the add-ons repo.