fetch-latest-release
fetch-latest-release copied to clipboard
Node 12 runtime is being deprecated for GitHub Actions
Hi Greg, Node 12 is being deprecated for GitHub Actions and this workflow is using Node 12 runtime, would be great to create a PR to update the using:
property here: https://github.com/gregziegan/fetch-latest-release/blob/01cabb047f189586793b7493e4fb5a0b5a815359/action.yml#L9
"Node 12 has been out of support since April 2022, as a result we have started the deprecation process of Node 12 for GitHub Actions. We plan to migrate all actions to run on Node16 by Summer 2023. We will monitor the progress of the migration and listen to the community for how things are going before we define a final date. To raise awareness of the upcoming change, we are adding a warning into workflows which contain Actions running on Node 12. This will come into effect starting on September 27th."
What you need to do: For Actions maintainers: Update your actions to run on Node 16 instead of Node 12 (Actions configuration settings) For Actions users: Update your workflows with latest versions of the actions which runs on Node 16 (Using versions for Actions) Reference: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
^^^ yes please!
+1 Please. It is a useful action.
https://github.com/gregziegan/fetch-latest-release/pull/17
Hello everyone, I am not sure if the maintainer is still working on this. Respectfully, I appreciate Greg for working on this action. I have forked this Action and resolved the deprecation warnings as you can see here https://github.com/CityOfLosAngeles/fetch-latest-github-release with changes that includes our added unit tests and example workflow runs. However, testing it out in another repository as a composite action is not working as it can't read the configuration for some reason. I am not sure we are able to dedicate substantial time to our fork soon but feel free to take a look as it might be a simple fix we are not seeing at the moment.
Our fork has been fixed and should be a drop in replacement resolving this issue and that of #14 , https://github.com/CityOfLosAngeles/fetch-latest-github-release
Jaylen,
Many thanks for your fork, it really is such a useful action.
I can confirm I have tested with a release flagged as 'Latest' followed by a release not flagged as 'Latest' and your action performs correctly in both instances.
Thanks again.