The Github action hasn’t be updated in 2024 and it’s not using Node LTS.
This is blocking all the CIs that are deploying using Github actions.
I thought that “easy deploys” was one of the core business on Fly.io
Am I deploying the wrong way?
The Github action hasn’t be updated in 2024 and it’s not using Node LTS.
This is blocking all the CIs that are deploying using Github actions.
I thought that “easy deploys” was one of the core business on Fly.io
Am I deploying the wrong way?
Hi @grebonato
thanks for raising this. If your CI is blocked right now, could you share the exact error message (or better, a link to a failing CI run)?
To clarify: in the flyctl-actions repo, setup-flyctl currently targets Node 20. I believe Node 20 is an LTS line and is supported today, though It does reach upstream EOL on 30 April, so we agree it should be bumped to the next supported LTS.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.