Bump every external action to the latest version as of the time of this PR's creation.
This resolves some warnings that might turn into errors fairly soon (I think depending on whether any of our currently specified versions break when it's forced to use Node20?). The summary of our workflow runs contained (cleaned up):
Node.js 16 actions are deprecated.
Please update the following actions to use Node.js 20:
On June 30th 2024, we will change the default from Node16 to Node20.
To opt out of this and continue using Node16 while it is still available in the runner, you can choose to set ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true
We will then continue to monitor Node16 usage and will communicate a timeline for the removal of Node16 at the start of October, based on the volume of continued use. This means that customers who use the environment variable to continue to use Node16 now have until October to complete their migrations.
Still, let's upgrade.
I believe the major version bumps in the Docker actions are just for the Node 20 bump (because that raises the minimum version of the Runner for GitHub Actions).
Bump every external action to the latest version as of the time of this PR's creation.
This resolves some warnings that might turn into errors fairly soon (I think depending on whether any of our currently specified versions break when it's forced to use Node20?). The summary of our workflow runs contained (cleaned up):
In March 2024, GitHub stated they'd enforce Node20 on 2024-06-03:
but they backpedalled a couple of weeks ago:
Still, let's upgrade.
I believe the major version bumps in the Docker actions are just for the Node 20 bump (because that raises the minimum version of the Runner for GitHub Actions).
See the release pages:
If we print the action versions used in this repo with:
Before this PR:
With this PR: