Thanks!

One more suggestion. Can we detect when this warning is emitted and emit a second warning pointing to the issue for more information (only if the original warning is also emitted)?

Hm.. that's an interesting idea. I'm not sure actually, I think it will be more clear once the warning is actually emitted. But so far I don't think we've used a mechanism to catch underlying Actions warnings.

After the warning starts being emitted, it will be emitted for every workflow run? If so, we can wait until it's emitted and then include a custom warning that links to the issue.

After the warning starts being emitted, it will be emitted for every workflow run? If so, we can wait until it's emitted and then include a custom warning that links to the issue.

Yes, I think so — at least that's what I understood from the Changelog post: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/