Describe the Problem
Current GitHub actions warn about Node 20 deprecation. They are appearing in Build Verifications, Publish Assets, etc workflows annotations.
These warnings contain the following link:
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
I cannot assess the impact myself, but there was a previous similar Feature Request for handling Node 12 deprecation (and I couldn't find one for Node 20):
#3930
The Solution you'd like
An assessment from someone in the know and a proactive fix if needed.
Alternatives that you've considered.
Not raise a ticket for it, but then "Node20 will reach end-of-life (EOL) in April of 2026" seems significant to raise on people's radar if it was not already.
Additional Context
Example screenshot of current warnings coming out of a Build Verification actions workflow:
Describe the Problem
Current GitHub actions warn about Node 20 deprecation. They are appearing in Build Verifications, Publish Assets, etc workflows annotations.
These warnings contain the following link:
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
I cannot assess the impact myself, but there was a previous similar Feature Request for handling Node 12 deprecation (and I couldn't find one for Node 20):
#3930
The Solution you'd like
An assessment from someone in the know and a proactive fix if needed.
Alternatives that you've considered.
Not raise a ticket for it, but then "Node20 will reach end-of-life (EOL) in April of 2026" seems significant to raise on people's radar if it was not already.
Additional Context
Example screenshot of current warnings coming out of a Build Verification actions workflow: