The node v12 deprecation notification needs more details

[tripleee]

Select Topic Area

Product Feedback

Body

My build jobs get a warning banner with a link to https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

However, the information on that page is not directly actionable. I have no actions which use Node for anything directly.

Fortunately, my jobs were simple enough that it was not hard to figure it out - the only external action I was using was uses: actions/checkout@v2 and by perusing the documentation for this action at https://github.com/actions/checkout I saw some notes about an upgrade to Node 16. However, upgrading to actions/checkout@v3 was apparently insufficient - can you tell me what more I need to fix?

https://github.com/tripleee/sloshy/actions/

Projects with more complex build dependencies will definitely have much more trouble just to figure out why they are seeing a warning. Could you include a note in the banner which explains which precise part of a job's configuration is causing the banner to be displayed?

[tripleee]

Similarly for https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ -- I see a banner with a link to this notification, but I have nothing in my build jobs which uses this feature.

[tripleee]

Actually, upgrading to v3 was sufficient for the nightly job. The other job had a second dependency which also required upgrading. The request to improve visibility as to what produces this warning in any particular workflow still stands, emphatically (if you can stand emphatically).