Github will begin reinforcing using Node16-based actions, as they migrate from Node 12. The reinforcement will begin on May 18, 2023. This change prevents the workflow from breaking when that date comes.
I've also taken the time to clean up the workflow, fixing up errors such as caching keys and checking out submodules (which are not in use anymore)
This was pain
Github will begin reinforcing using Node16-based actions, as they migrate from Node 12. The reinforcement will begin on May 18, 2023. This change prevents the workflow from breaking when that date comes.
I've also taken the time to clean up the workflow, fixing up errors such as caching keys and checking out submodules (which are not in use anymore)